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.
- depends on
-
JENKINS-28438 OS X installation - force use of Java 7 or 8
-
- Resolved
-
-
JENKINS-28231 Java Version hard coded to Java6
-
- Resolved
-
- is blocking
-
JENKINS-27624 Upgrade minimum require Java version from 7 to 8
-
- Resolved
-
- is duplicated by
-
JENKINS-28197 Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
-
- Resolved
-
-
JENKINS-27623 Upgrade minimum require Java version from 6 to 7
-
- Resolved
-
- is related to
-
JENKINS-25272 remoting-2.46.jar breaks JDK 5 Maven builds
-
- Resolved
-
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.