Upgrade core framework build to JDK 17 #17778
2 votes, 12 watchers
The text was updated successfully, but these errors were encountered:
Sam Brannen commented
Hi Juergen Hoeller,
I've got some good news...
If you remove the
Of course, lots of things don't work, such as: JAXB, XmlBeans, AspectJ, JRuby, our shadow ClassLoader for JPA tests, etc.
As an experiment, however, I was able to get the JAXB support in Spring OXM to compile by declaring the following dependencies in
xjc 'javax.xml.bind:jaxb-api:2.2.11' xjc 'com.sun.xml.bind:jaxb-core:2.2.11' xjc 'com.sun.xml.bind:jaxb-impl:2.2.11' xjc 'com.sun.xml.bind:jaxb-xjc:2.2.11' xjc 'javax.activation:activation:1.1.1'
So.... happy testing! ;)
p.s., I read elsewhere that the preferred way to reference the current JAXB dependencies (without referencing com.sun.*) is as follows:
Rostislav Krasny commented
Juergen Hoeller, I think the minimum JDK version for Spring Framework 6 building should be JDK 11 because this is the first Long Term Support (LTS) version of JDK after JDK 8. JDK 9 and JDK 10 had very short term support and are already dead, i.e. they are unsupported by Oracle. I think the title of this Jira ticket should be updated accordingly.
Juergen Hoeller commented
Good point, once we upgrade the Java baseline for Spring Framework 6, we'll certainly aim for JDK 11+ right away. However, from where we stand right now, this is unlikely to happen before 2021 (when JDK 17 is on the horizon as the next LTS release, providing us with a target support range of two LTS generations of Java again).
Prior to this commit, the Javadoc task would fail on `spring-context-indexer` and `spring-instrumentation`. It seems that missing remote docs or HTTP redirects were failing the process. This commit removes the missing published Javadocs and updates the version for the JDK API. See gh-17778