But, Java 8 will stop receiving public updates next year, and pretty much everywhere I've looked, folks are sticking on Java 8.
I am hoping I'm wrong, but I wonder if we will see Java 8 be forked, and live on, by community effort, as the cost to maintain it would be lower than the cost of risking moving to Java 11. For a lot of businesses, I don't think the reality has set in yet, and I don't think they're going to realize what situation they're in until Java 8 hits EOL.
This is nothing new.
However stuff like JDBC interface changes comes up as breaking changes in previous releases.
In what concerns Java 9, Mark Reinhold keeps doing presentations about how all Java relevant frameworks and tools are already Java 9 compliant. Including many that they validated against in Maven repositories.
Last presentation I saw was at FOSDEM.
So it appears to be a major issue to anyone wanting to migrate Java 9 without updating the frameworks as well, having some kind of special case library, or using APIs that were always documented as internal.
EDIT: Maybe it's outdated; SLF4J and Netty do claim to be JDK9-ready.
[0]: https://wiki.openjdk.java.net/display/quality/Quality+Outrea...
https://www.oracle.com/technetwork/topics/security/poodlecve...
There's a lot more but it of course depends on the subset of the JDK that you're using. Look over the release notes for historical JDK updates.