Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28368

Error "JDK 5 not supported to run Maven" while running Java 6

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

      Hi,

      I don't know why this problem appeared today, when running a job using Java 6, we got the following error:
      ERROR: JENKINS-18403 JDK 5 not supported to run Maven
      And then Jenkins switched to Java 7 (which we don't want).

      You can see the whole log here: http://jenkins.petalslink.com/view/81%20-%20Petals%20ESB%20Enterprise%204.3.x/job/4.3.x%20-%20Petals%20Components%20-%20CDK%20-%20Parent%20POM/2/console

      I checked the source code, and I guess a UnsupportedClassVersionError happened.
      It would maybe best to log the exception when it does to at least ease diagnostic if the problem is coming from us… but I don't think it is the case because it happens really at the beginning of the execution…

      Thanks!

          [JENKINS-28368] Error "JDK 5 not supported to run Maven" while running Java 6

          Victor Noël added a comment -

          I am wondering if it's not related to the fact that the maven31-agent.jar and co are compiled using Java 7 since Jenkins only support Java 7… but these artifacts should be able to support older version of Java even though Jenkins does not, no?

          Because it becomes impossible to use something else than Java 7 to execute jobs in Jenkins then…

          Victor Noël added a comment - I am wondering if it's not related to the fact that the maven31-agent.jar and co are compiled using Java 7 since Jenkins only support Java 7… but these artifacts should be able to support older version of Java even though Jenkins does not, no? Because it becomes impossible to use something else than Java 7 to execute jobs in Jenkins then…

            Unassigned Unassigned
            victornoel Victor Noël
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: