- Add a useModulePath switch to the testCompile mojo ( #119) - Allow dependency exclusions for 'annotationProcessorPaths' ( #173) - Use maven-resolver to resolve 'annotationProcessorPaths' dependencies ( #169) - upgrade plexus-compiler to improve compiling message ( #164) - compileSourceRoots parameter should be writable ( #159) - Change showWarnings to true by default ( #157) - Warn about warn-config conflicting values ( #153) - Update default source/target from 1.7 to 1.8 ( #149) - display recompilation causes ( #143) - add some parameter to pattern from stale source calculation ( #141) - dedicated option for implicit javac flag ( #102) Bug Fixes.

Sourced from maven-compiler-plugin's releases.

It is also very unfortunate that we can't use OpenJDK11.Bumps maven-compiler-plugin from 3.10.1 to 3.11.0. But we can't find that package back on package share. , it is mentioned that we can download an Adobe licensed Java 11 from package share. My question is: how to upgrade Java version after an AEM in-place upgrade? Is this a supported flow or will AEM 6.5 only work with Java 11 when it was initially installed with Java 11? So not in case of an in-place upgrade? It seems that when we try to boot the AEM 6.5 instance with Java 11, it corrupts the launchpad. Reverting back to Java 8 also doesn't work anymore. This does not seem to work as we are getting a lot of errors related to '(: jdk/internal/reflect/MethodAccessorImpl)'.

Once the in-place upgrade is done, we want to restart our AEM 6.5 instance with Java 11. For the upgrade procedure we use the same java version 8. We are now performing in-place upgrade to AEM 6.5. We have an on-prem AEM 6.3 installation running with Oracle Java 8.

Upgrade java 8 to 11