Closed d021248 closed 5 years ago
Dear @d021248
This issue is solved with version 2.0.0
:
https://search.maven.org/search?q=com.sap.cloud.security
Please consider the release notes: https://github.com/SAP/cloud-security-xsuaa-integration/releases/tag/2.0.0
Best regards, Nena
We have switched the security library from
com.sap.xs2.security/java-container-security-api
(old) tocom.sap.cloud.security.xsuaa/java-container-security
(new) .We have excluded all implicite references to the old library in our pom.xml.
However, some cloud foundry runtime components still use the older version of the library (e.g. Buildpack).
The problem is now, that both libraries (old and new) have identical package names and identical class names. This makes consumption of the desired library difficult and makes debugging cumbersome, since we cannot easily determine which version of the lib we are confronted with.
We are forced to implement hacks to get this resolved:
Would it be possible to have different package names for the libraries, which would allow a co-existence of both libs and allow a unequivocal usage of the desired version?
Please don't hesitate to contact me in case of questions.