java-sproc-wrapper
java-sproc-wrapper copied to clipboard
zalando-stups
update Readme
@vadeg We should inform users that they need to move their custom objectTransformer to the new default package, or they need to provide scanning namespace instead of supporting the old namespace ("de.zalando") ( https://github.com/zalando-stups/java-sproc-wrapper/pull/68)
It is solution for https://github.com/zalando-stups/java-sproc-wrapper/issues/67
@vadeg It doesn't make sense to support old namespace for new version of the library since the library provides to the clients an alternative path to scan value-transformer via "global.value.transformer.search.namespace" system env key. So instead of making changing "global.value.transformer.search.namespace" to the array, it would be better to keep it as it is and inform the client that they need to change directory of their value-transformer to "de.zalando". Or if they don't want to change it they can provide their existing directory via "global.value.transformer.search.namespace". So that's why I closed https://github.com/zalando-stups/java-sproc-wrapper/pull/68 and created this one for updating README.md.
@mesut readme update would be helpful, bu I think support of multiple packages also make sense. Library provide a UUIDValueTransformer global value transformers out of the box. If someone wants to use that, then it enforces to keep all transformers in the org.zalando package what may not match with packages in other projects.
Vulnerabilities found. Need to fix them first
One or more dependencies were identified with vulnerabilities: Error:
Error: postgresql-42.2.14.jar: CVE-2022-21724, CVE-2022-31197, CVE-2022-26520 Error: spring-core-5.2.16.RELEASE.jar: CVE-2021-22060, CVE-2021-22096, CVE-2022-22968, CVE-2022-22965, CVE-2022-22971, CVE-2022-22950, CVE-2016-1000027, CVE-2022-22970