I just changed the build to use Java 8 for running Maven (not for compilation/testing) [On the basis that one starts by fixing the easy issues]
This has got rid of the warning about using an incompatible Java. Furthermore it seems to have fixed the main problem. Looks like when Jenkins retries using a different Java that it somehow mangles the javac command line. On 10 January 2018 at 09:28, Stefan Bodewig <[email protected]> wrote: > Hi all > > has anybody got any idea why javac should suddenly start using --release > for a Java7 javac on the windows boxes but not for Linux? > > I recall Gary updatng all kinds of Maven plugins as well as infra > updating the jenkins nodes to run Java9 but the build explicitly selects > Java7 - and this kind of configuration seems to work for the Matrix > build. > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
