Some projects want to use devon but only in a pick&choose form with minimum dependencies. In oasp4j-security a dependency to mmm-util-core was used only to reuse some simple exceptions. That is nice in general and gives exceptions with I18N as we propose but for some reasons in some projects we have to "fight" for each dependency and therefore minimizing makes our life simpler.
After merging this PR the security module should be functionally same except for using simpler standard JDK runtime exceptions in some sepcific error cases (for usage that is deprecated anyhow).
Some projects want to use devon but only in a pick&choose form with minimum dependencies. In
oasp4j-securitya dependency tommm-util-corewas used only to reuse some simple exceptions. That is nice in general and gives exceptions with I18N as we propose but for some reasons in some projects we have to "fight" for each dependency and therefore minimizing makes our life simpler. After merging this PR the security module should be functionally same except for using simpler standard JDK runtime exceptions in some sepcific error cases (for usage that is deprecated anyhow).