-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Jakarta EE 10 #13
Comments
Hi @Thopap I agree that we should create a version 3.x that is J2EE 10+ and keep the version 2.x for J2EE 8 (as long as needed). |
This was already the my plan to provide a PR :-) I was just not able to assign this ticket to myself. |
* Update to java 11 * switch to jakarta xml bind * some dependency updates BREAKING CHANGE: Java 11 is now required and J2EE 10
* Update to java 11 * switch to jakarta xml bind * some dependency updates
…rsion 2.x with requirements (#13) (semver: skip)
* Update to java 11 * switch to jakarta xml bind * some dependency updates
* Update to java 11 * switch to jakarta xml bind * some dependency updates
done in pr #14 |
I am going to release a new version (3.0.0) this week ... |
…rsion 2.x with requirements (#13) (semver: skip)
…rsion 2.x with requirements (#13) (semver: skip)
Release is created (https://github.com/prolutionsGmbH/herasaf-xacml-core/releases/tag/3.0.2) and available from maven central. |
Currently heras-xacml use the jaxb-api from the javax.xml.bind namespace (J2EE 8). To allow the usage of Heras also with J2EE 10+ compatible applications an update to jakarta xml-bind 4.0 should be done (which use the package jakarta.xml.bind for the jaxb annotations).
Since this change will introduce a incompatible change, a Heras 3.x version is needed.
The text was updated successfully, but these errors were encountered: