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

EOL JENKINS-20679

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • plugin-pom

      Previously Java versions strings were 1.x, so the plugin-pom hardcodes a java.level property of "8" like so:

      <source>1.${java.level}</source>

      See: https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L604

      https://blog.codefx.org/java/java-9-migration-guide/#New-Version-Strings

      But that won't work if we need to use a version of 9+, where the version string is now just "9" etc

      In general we need multi-release JAR support here because if we change the way the java.level is handled then we don't inadvertently break Java 8 or earlier which expect the 1.x format.

          [JENKINS-52014] EOL JENKINS-20679

          Sam Van Oort created issue -
          Sam Van Oort made changes -
          Epic Link New: JENKINS-40689 [ 177392 ]

          Oleg Nenashev added a comment -

          I would vote against Java9-only plugins in short term.
          We likely need to get the Multi-Release JAR support in Jenkins tooling over the fence

          Oleg Nenashev added a comment - I would vote against Java9-only plugins in short term. We likely need to get the Multi-Release JAR support in Jenkins tooling over the fence

          Sam Van Oort added a comment -

          I would agree with that being a better solution – perhaps I should rephrase the issue to better express the problem.

          Sam Van Oort added a comment - I would agree with that being a better solution – perhaps I should rephrase the issue to better express the problem.
          Sam Van Oort made changes -
          Summary Original: Plugin-Pom Can't Handle New Java 9+ Version strings for java.level New: Plugin-Pom Uses Single Version String Hardcoded To Only Work With Java 8 or earlier
          Sam Van Oort made changes -
          Description Original: Previously Java versions strings were 1.x, so the plugin-pom hardcodes a java.level property of "8" like so:

          <source>1.${java.level}</source>

          See: https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L604

          https://blog.codefx.org/java/java-9-migration-guide/#New-Version-Strings

          But that won't work if we need to use a version of 9+, where the version string is now just "9" etc           		New: Previously Java versions strings were 1.x, so the plugin-pom hardcodes a java.level property of "8" like so:

          <source>1.${java.level}</source>

          See: https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L604

          https://blog.codefx.org/java/java-9-migration-guide/#New-Version-Strings

          But that won't work if we need to use a version of 9+, where the version string is now just "9" etc

          In general we need multi-release JAR support here because if we change the way the java.level is handled *then* we don't inadvertently break Java 8 or earlier which expect the 1.x format.
          Sam Van Oort made changes -
          Summary Original: Plugin-Pom Uses Single Version String Hardcoded To Only Work With Java 8 or earlier New: Plugin POM Uses Single Version String Hardcoded To Only Work With Java 8 or earlier
          jang hyemi (Inactive) made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          jang hyemi (Inactive) made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Oleg Nenashev made changes -
          Labels Original: java10 java10_hackathon New: java10 java10_hackathon java11

            basil Basil Crow
            svanoort Sam Van Oort
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: