The Java 9 change was to remove access to unofficial APIs. I agree it was somewhat painful, but not nearly to the level of the 2->3 change which ended up chang

The Java 9 change was to remove access to unofficial APIs. I agree it was somewhat painful, but not nearly to the level of the 2->3 change which ended up changing python syntax. Most dependencies worked throughout the change and still work. > Furthermore, whenever you get the likes of Lombok or something that has any dynamic compilation ... there's less smooth sailing. Not sure about c3p0, but Lombok goes out of it's way to inject itself into javac internals in order to make it's output changes. It's using the most internal of internal code in order to make that @Getter annotation work. Plenty of other annotation processing APIs are completely unaffected by javac updates because they choose not to use internal APIs. Immutables, Autovalue, dagger2, all examples of dynamic compilation that continue to work regardless the version of java. Lombok is a horrible little dependency that I wish people would abandon. It's making a mess and then complaining that it's somehow Java's fault because Lombok decided it needed access to the AST. I get it, things have broken. But what has been broken is literally the undefined and non-public APIs which went so far as to call their packages things like `sun.misc.unsafe` just to try and ward off people from using these APIs. (With the javadocs to boot which told people not to use this). And even with the break, the Java devs went out of their ways to make stand-in apis.