Closed
Description
Juergen Hoeller opened SPR-16391 and commented
JDK 11 is currently scheduled for September 2018. Not expecting any major changes beyond JDK 10 from our perspective, we should be able to fully support it in the 5.1 line already. Ideally our framework build would be able to run on JDK 8, 9, 10 as well as 11, even if our own test efforts will focus on JDK 8 and 11 (as the official long-term support branches) at that point.
Issue Links:
- Compatibility with JDK 9 GA [SPR-15992] #18941 Compatibility with JDK 9 GA ("depends on")
- Compatibility with JDK 10 [SPR-16390] #20936 Compatibility with JDK 10 ("depends on")
- Upgrade to ASM 6.2 [SPR-16398] #20944 Upgrade to ASM 6.2 ("depends on")
- Upgrade to ASM 7.0 [SPR-17267] #21800 Upgrade to ASM 7.0 ("depends on")
- MethodHandles.Lookup.defineClass for CGLIB class definition purposes [SPR-15859] #20414 MethodHandles.Lookup.defineClass for CGLIB class definition purposes ("depends on")
- Classpath scanning does not work in tests using the module path [SPR-16977] #21515 Classpath scanning does not work in tests using the module path
- Classpath scanning on inner classes fails against JDK 11 bytecode level [SPR-17096] #21633 Classpath scanning on inner classes fails against JDK 11 bytecode level
- Classification of ClassCastExceptions doesn't work in JDK 11 (OpenJDK) [SPR-17093] #21630 Classification of ClassCastExceptions doesn't work in JDK 11 (OpenJDK)
- DATACMNS-1373 Align class loading in ClassGeneratingEntityInstantiator with ClassGeneratingPropertyAccessorFactory
Referenced from: commits 93bb78e, 5094941
2 votes, 13 watchers