[JENKINS-68462] Prepare LDAP for removal of JAXB and Java 11 requirement #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See JENKINS-68462. The current version of this plugin bundles an old version of
spring-ldap-core
, which requires JAXB. When we start requiring Java 11, JAXB will not be available except as a plugin-to-plugin dependency (which this plugin does not have). In spring-projects/spring-ldap#590spring-ldap-core
2.3.5 and later stopped requiring JAXB. This PR updates the core baseline to 2.332.x, which pulls in a newer version ofspring-security-bom
, which pulls inspring-ldap-core
2.3.5 (2.303.x pulls in 2.3.4, sadly). Thus with this update we start shippingspring-ldap-core
2.3.5 which no longer depends on JAXB, and thus we are assured of a smooth upgrade for users when we start requiring Java 11.Testing done