You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Unfortunately, the Groovy 2.5.1 compiler still isn't JDK 11 compatible... apparently due to its use of ASM 6.2 without the ASM 7 experimental option (see #21633 for a similar case on our end). As a consequence, our build still doesn't run on JDK 11 (build 25).
As of 5.1.1, we run the build against Groovy 2.5.3 which executes fine on JDK 11. Including an upgrade of spring-test to use Hibernate ORM 5.3.6 instead of 5.2.17, this makes our entire build pass on JDK 11 now.
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:
Referenced from: commits 93bb78e, 5094941
2 votes, 13 watchers
The text was updated successfully, but these errors were encountered: