On Wed, 2017-06-28 at 00:49 +0100, sebb wrote: > It's only Maven projects that have to be run with Java 8 on Jenkins. > And this only affects the Maven framework. > > Compilation and testing can still be done with earlier Java versions. > > Commons has lots of components that target Java 6 or even 5, and they > work fine with current Jenkins (which needs Java 7). >
It does not look that way to me. I understand one can still spawn any arbitrary process with Jenkins as a job but this is not the same as having full Maven project support. --- [httpcomponents-client-4.5.x] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m -cp /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/apache-maven-3.3.9 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven33-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 39826 Native maven support requires Java 1.7 or later, but this Maven is using /usr/local/asfpackages/java/jdk1.6.0_45-64/jre Please use the freestyle project. ERROR: Failed to launch Maven. Exit code = 1 Sending e-mails to: [email protected] Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped Finished: FAILURE --- Oleg > The Jenkins JVM requirement is not directly relevant to HC (or any > other project), and should not be used to drive a change. > > On 27 June 2017 at 16:35, Gary Gregory <[email protected]> > wrote: > > Giving up Java 7 works for me. It is not clear to me that the > > Jenkins > > update does not support Java 7 at all though: > > > > "If your Maven projects need to be built with JDK 7, consider > > converting > > them to freestyle projects, or look into Maven toolchains." > > > > We use Maven toolchains over at Log4j (for building some bits with > > Java 9) > > and that works fine. > > > > The business SSH slaves does not sound pretty though. > > > > Travis-CI still supports Java 7 of course so we can go with that. > > > > We just need to decide what matters for 5.0 and 4.6. Java 8 is OK > > here. > > > > Gary > > > > On Jun 27, 2017 04:22, "Oleg Kalnichevski" <[email protected]> > > wrote: > > > > Folks > > > > ASF Jenkins will no longer support Java7 Maven projects soon. That > > means there will be no way to reliably test Java 7 compatibility > > anymore. > > > > Maybe it is time we gave up on Java 7 compatibility altogether. By > > the > > time 5.0.x projects go GA Java 7 may no longer matter. > > > > What do you think? > > > > Oleg > > > > > > -------- Forwarded Message -------- > > From: Gavin McDonald <[email protected]> > > Reply-to: [email protected] > > To: [email protected] > > Cc: ASF Operations <[email protected]> > > Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade > > (And > > JDK7 deprecation) > > Date: Tue, 27 Jun 2017 17:03:13 +1000 > > > > ... > > > > > > 2. Upgrade of Jenkins - Jenkins project released a new LTS release, > > version 2.60.1. This is a major release and breaks > > Jenkins in terms of Maven jobs for JDK 7 in the same way that > > it > > happened for Maven and JDK 6 a few months back. > > > > The infra team (mainly myself) got quite some feedback on not > > supplying advance notice of this breakage. That upgrade > > however was necessary due to security fixes that required our > > upgrade. This email serves as advance warning of the > > upcoming upgrade of Jenkins, the downtime due to the migration > > of > > the service to a new host; and notice of the breakage > > to JDK 7 that the upgrade brings. > > > > Please familiarise yourself with the Jenkins LTS upgrade notes > > at > > [1]. > > In particular please note:- > > > > “…2.60.1 is the first Jenkins LTS release that requires Java 8 > > to > > run. If you're using the Maven Project type, please note that it > > needs > > to use a JDK capable of running Jenkins, i.e. JDK 8 or up. If you > > configure an older JDK in a Maven Project, Jenkins will attempt to > > find > > a newer JDK and use that automatically. If your SSH Slaves fail to > > start and you have the plugin install the JRE to run them, make > > sure to > > update SSH Slaves Plugin to at least version 1.17 (1.20 > > recommended). > > ... > > > > ----------------------------------------------------------------- > > ---- > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
