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

Upgrade maven embedder from 3.1.0 to at least 3.5.4

    XMLWordPrintable

Details

    Attachments

      Issue Links

        Activity

          ianw Ian Williams added a comment -

          Fully agree on dropping maven2 support as EOL, but raising minimal version requires justification. Many large enterprises have large legacy codebases built on maven 3.1.1 (and JDK 6).

          An arbitrary change to minimal version will have negative impacts across many plugins, effectively freezing our installed Jenkins configuration.

          I hear the "buts" - using jdk 6 and M3.1.1 also has repercussions, but is there a justifiable reason to raise the minimal version ?

          ianw Ian Williams added a comment - Fully agree on dropping maven2 support as EOL, but raising minimal version requires justification. Many large enterprises have large legacy codebases built on maven 3.1.1 (and JDK 6). An arbitrary change to minimal version will have negative impacts across many plugins, effectively freezing our installed Jenkins configuration. I hear the "buts" - using jdk 6 and M3.1.1 also has repercussions, but is there a justifiable reason to raise the minimal version ?
          ianw Ian Williams added a comment -

          olamy, You have now revised the subject and thus intent of the change. My question still remains; what is the motivation to move up. As noted this will impact many users who are still using legacy maven 3.1.1 (and JDK 6)., effectively freezing the Jenkins configuration since jdk 1.7 would now be the minimum.

          ianw Ian Williams added a comment - olamy , You have now revised the subject and thus intent of the change. My question still remains; what is the motivation to move up. As noted this will impact many users who are still using legacy maven 3.1.1 (and JDK 6)., effectively freezing the Jenkins configuration since jdk 1.7 would now be the minimum.
          olamy Olivier Lamy added a comment -

          Simple example if you use wildcard exclusions your build will fail because it's available only with maven 3.3.3 and the current embedder will reject the pom as a failure whereas it's not.

          This plugin has some technical constraints (defaults..) so it's impossible to manage such legacy builds and upgrade for new features and/or security reasons.

          BTW we are now in 2019j jdk6 and jdk7 are definitely EOL/DEAD

          one day we have to stop trying to maintain those very old/legacy...

          If it's a big issue for you you can definitely use freestyle or pipeline plugins, use maven toolchain, configure compiler target/source attributes, animal-sniffer plugin.... few options.

           

          olamy Olivier Lamy added a comment - Simple example if you use wildcard exclusions your build will fail because it's available only with maven 3.3.3 and the current embedder will reject the pom as a failure whereas it's not. This plugin has some technical constraints (defaults..) so it's impossible to manage such legacy builds and upgrade for new features and/or security reasons. BTW we are now in 2019j jdk6 and jdk7 are definitely EOL/DEAD one day we have to stop trying to maintain those very old/legacy... If it's a big issue for you you can definitely use freestyle or pipeline plugins, use maven toolchain, configure compiler target/source attributes, animal-sniffer plugin.... few options.  
          olamy Olivier Lamy added a comment - - edited

          ianw for 2years now Jenkins core require 1.8...    https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/ 

          olamy Olivier Lamy added a comment - - edited ianw for 2years now Jenkins core require 1.8...    https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/  

          People

            olamy Olivier Lamy
            olamy Olivier Lamy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: