Excellent to see some work on this! Whilst I obviously have Java 8 around since most components target it currently and so its my main build env, I do also have envs that default to 11 and as you later said its really annoying having to tweak the env back to 8 just to build a given component there for e.g trying something out.
I would however say there should be CI that uses JDK11 (+newer, 15EA is out) once building with it works, to ensure that it is kept working too where desired. Obviously this would be in addition to 8 given its what the releases target. Given the variety of CI envs available (Travis, Appveyor, GitHub Actions, the ASFs Jenkins env, etc) its fairly easy to hit a variety of JDK versions. Robbie On Fri, 8 May 2020 at 11:24, Emmanuel Hugonnet <[email protected]> wrote: > > Hello, > > When i need to work on Apache ActiveMQ Artemis I need to switch my local > environement to use OpenJDK 8 instead of the default OpenJDK 11 > which I use to develop. > > I have started a branch > https://github.com/ehsavoie/activemq-artemis/tree/java_11 which builds on > OpenJDK 8 and 11 with the fast-tests profile. > > mvn clean install -Pfast-tests is passing for me locally :) > > I don't think that the CI or the release should use Java 11 but I hope this > will smoothen the time when the migration occurs. > > Also I couldn't use the --release 8 flag for OpenJDK 11 because of the use of > Unsafe, if someone has a better alternative I'm all hears. > > Do you want me to sumbit a PR for this ? Does this make sense to the > community ? > > Emmanuel > > >
