Closed
Description
Juergen Hoeller opened SPR-13344 and commented
As of 4.2.1, the core Spring Framework is fully compatible with mid-2015 JDK 9 builds already, at runtime as well as for running the framework build.
For 4.3, we aim for full runtime compatibility with the merged JDK 9 mainline, including the current state of the Jigsaw module system which has been developed in a parallel branch for a long time. Note that this not include any actual support for JDK 9 modules yet; this remains a Spring 5 topic.
Issue Links:
- Stable module names for Spring Framework jars on JDK 9 module path [SPR-13716] #18289 Stable module names for Spring Framework jars on JDK 9 module path ("is depended on by")
- Upgrade core framework build to JDK 17 #17778 Upgrade core framework build to JDK 11 ("is depended on by")
- Out-of-the-box build compatibility with JDK 9 build 136 [SPR-14645] #19211 Out-of-the-box build compatibility with JDK 9 build 136 ("is depended on by")
- Upgrade build to Gradle 3.0 [SPR-14569] #19138 Upgrade build to Gradle 3.0
- Document Spring recommendations/restrictions for Java 9 module setups [SPR-14579] #19148 Document Spring recommendations/restrictions for Java 9 module setups
- Remove use of Boolean constructors in tests [SPR-15076] #19642 Remove use of Boolean constructors in tests
- Avoid use of double constructor of BigDecimal in tests [SPR-15077] #19643 Avoid use of double constructor of BigDecimal in tests
- Avoid deprecated Class.newInstance in favor of constructor-based instantiation [SPR-14486] #19055 Avoid deprecated Class.newInstance in favor of constructor-based instantiation
- SerializableTypeWrapper should reobtain type accessors from declaring interface [SPR-14487] #19056 SerializableTypeWrapper should reobtain type accessors from declaring interface