4 ms·
We are at JDK 8 now too and will move towards the next LTS (JDK 11) near the end of the year. The transition from Java 8 to Java 11 feels more involved than the
by Freak_NL 8y ago
We are at JDK 8 now too and will move towards the next LTS (JDK 11) near the end of the year. The transition from Java 8 to Java 11 feels more involved than the transition from Java 7 to Java 8 was. Everything seems to work, but a lot of major libraries are still throwing lots of warnings, and to really get the most out of the transition developers and existing codebases should get comfortable with the new module system as well.
Moving to a non-LTS release (12) is a non starter of course.
- chipperyman573 8y ago>The transition from Java 8 to Java 11 feels more involved than the transition from Java 7 to Java 8 was I don't know a whole lot about Java 7 vs 8 vs 11, but wouldn't that make the most sense? 7->8 is one version upgrade, 7->11 is 4.
- pilif 8y ago9, 10 and 11 are following a new release schedule of timed releases (every 6 months), whereas 8 was still a traditional feature release. I would say that aside of the module system that came with a huge list of now inaccessible internal methods that a lot of dependencies relied on even though they shouldn’t have, there was even more change between 7 and 8 than there was between 8 and 11
- Freak_NL 8y agoYeah, Oracle changed what one major version upgrade meant from JDK 8 onwards. For production purposes JDK 9 and 10 effectively don't exist.
- tyingq 8y agoIt's kicking the can a bit, but there's the "--release 8" javac flag you can use in 11.