HHH-13043 + HHH-13116 Upgrade to JAXB 2.3 #2658
Closed
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.
https://hibernate.atlassian.net//browse/HHH-13043
https://hibernate.atlassian.net//browse/HHH-13116
I gave up on doing the upgrade for OSGi; it's just too early for that. We don't really have any code that is specific to JAXB 2.3, so tests work fine in karaf, which uses JAXB 2.2 in the classpath. I guess that's good enough for now?
The most important thing is that Maven users will finally be able to use ORM in a JDK11 environment, i.e. HHH-13116 will be fixed.
How to reproduce HHH-13116 and check that it's fixed
Due to the need to use Maven to reproduce HHH-13116, I didn't even try to add a reproducer in ORM itself. If you want to check that it is indeed fixed: