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]
