• Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • core

      This ticket tracks the promise made in http://jenkins-ci.org/content/good-bye-java6 that we are bumping up core requirements from Java6 to Java7.

          [JENKINS-28120] Jenkins core to require Java7

          Jesse Glick added a comment -

          If you wish to use the Maven project type, you must set the Jenkins project configuration to use JDK 7 or newer, which means the JVM used to run Maven itself. The JDK tools used to build and test your project’s code may be anything. These tools are defined by settings in Maven plugins, such as -Dmaven.compiler.executable=… on the Maven command line.

          Alternately, you can simply build your project using JDK 7+ tools but using tool configuration limiting the source code to earlier releases (such as -source 6), and using the Animal Sniffer plugin to block Java 7+ APIs from being used accidentally.

          If you wish to run the Maven process using anything older than Java 7, you must use the freestyle project type with the Maven build step—which I would strongly recommend for a variety of reasons anyway.

          Jesse Glick added a comment - If you wish to use the Maven project type, you must set the Jenkins project configuration to use JDK 7 or newer, which means the JVM used to run Maven itself. The JDK tools used to build and test your project’s code may be anything. These tools are defined by settings in Maven plugins, such as -Dmaven.compiler.executable=… on the Maven command line. Alternately, you can simply build your project using JDK 7+ tools but using tool configuration limiting the source code to earlier releases (such as -source 6 ), and using the Animal Sniffer plugin to block Java 7+ APIs from being used accidentally. If you wish to run the Maven process using anything older than Java 7, you must use the freestyle project type with the Maven build step—which I would strongly recommend for a variety of reasons anyway.

          We have some older slaves which run SunOS-5.9 for which Oracle does not provide Java7. Slave upgrade is not a solution either since there are some native legacy tools used in the build system which can only run on this machine. Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected?

          Krzysztof Malinowski added a comment - We have some older slaves which run SunOS-5.9 for which Oracle does not provide Java7. Slave upgrade is not a solution either since there are some native legacy tools used in the build system which can only run on this machine. Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected?

          Jesse Glick added a comment -

          Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected?

          Sounds that way, unless you can find an OpenJDK 7 port.

          Jesse Glick added a comment - Does this mean I will have to stop upgrading Jenkins in order to have SunOS-5.9 slaves connected? Sounds that way, unless you can find an OpenJDK 7 port.

          Victor Noël added a comment -

          Jesse, why would you strongly recommend to use the freestyle project type for Maven builds?

          I tried to look at it but there is two different build step available: invoke maven3 and invoke maven goal (or something like that, I am not using the english locale).
          Which one should then be used?
          And are dependencies taken into account to trigger the jobs as with the maven project type?
          Is there specific to do w.r.t. to the tests and the unstability of the build?

          Thank you for your help

          Victor Noël added a comment - Jesse, why would you strongly recommend to use the freestyle project type for Maven builds? I tried to look at it but there is two different build step available: invoke maven3 and invoke maven goal (or something like that, I am not using the english locale). Which one should then be used? And are dependencies taken into account to trigger the jobs as with the maven project type? Is there specific to do w.r.t. to the tests and the unstability of the build? Thank you for your help

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          pom.xml
          http://jenkins-ci.org/commit/jenkins/6496a946848204dc908c503452fc294c7daebb73
          Log:
          JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/jenkins/6496a946848204dc908c503452fc294c7daebb73 Log: JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime.

          dogfood added a comment -

          Integrated in jenkins_main_trunk #4155
          JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime. (Revision 6496a946848204dc908c503452fc294c7daebb73)

          Result = UNSTABLE
          kohsuke : 6496a946848204dc908c503452fc294c7daebb73
          Files :

          • pom.xml

          dogfood added a comment - Integrated in jenkins_main_trunk #4155 JENKINS-28120 Phase 2: allow the core to use Java7 syntax and runtime. (Revision 6496a946848204dc908c503452fc294c7daebb73) Result = UNSTABLE kohsuke : 6496a946848204dc908c503452fc294c7daebb73 Files : pom.xml

          Code changed in jenkins
          User: Mitoma Ryo
          Path:
          src/main/java/hudson/plugins/sshslaves/SSHLauncher.java
          http://jenkins-ci.org/commit/ssh-slaves-plugin/af2b72bd79577550623be685158bd2969284cff0
          Log:
          update JDK version.

          Jenkins became requiring JDK1.7.
          see JENKINS-28120 https://github.com/jenkinsci/jenkins/commit/c00935f0b212272c7b00dc446bdbab20a13bb787

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mitoma Ryo Path: src/main/java/hudson/plugins/sshslaves/SSHLauncher.java http://jenkins-ci.org/commit/ssh-slaves-plugin/af2b72bd79577550623be685158bd2969284cff0 Log: update JDK version. Jenkins became requiring JDK1.7. see JENKINS-28120 https://github.com/jenkinsci/jenkins/commit/c00935f0b212272c7b00dc446bdbab20a13bb787

          Jesse Glick added a comment -

          victornoel this is a user list question which is off topic here.

          Jesse Glick added a comment - victornoel this is a user list question which is off topic here.

          Paul Suh added a comment -

          OS X installer is broken due to this issue. See bug #28438. In addition, Apple has added an updated download link to the Java 6 dependency, https://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US.

          Paul Suh added a comment - OS X installer is broken due to this issue. See bug #28438. In addition, Apple has added an updated download link to the Java 6 dependency, https://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US .

          Jesse Glick added a comment -

          plsuh if you know of any regressions caused by this please make sure they are filed separately and marked as blocking this one. Do not reopen.

          Jesse Glick added a comment - plsuh if you know of any regressions caused by this please make sure they are filed separately and marked as blocking this one. Do not reopen.

            kohsuke Kohsuke Kawaguchi
            kohsuke Kohsuke Kawaguchi
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: