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

maven core extensions not working on maven-job

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      jenkins 2.232
      java 11.0.3 [AdoptOpenJDK (build 11.0.3+7)]
      maven 3.6.3
    • Similar Issues:

      Description

      as discussed with Olivier Lamy in maven mailing list thread here a standard maven job does not take core-extensions into consideration.

      Detailled instructions to reproduce can be found in the thread.

      Perhaps related to https://issues.jenkins-ci.org/browse/JENKINS-40621
       

        Attachments

          Activity

          Hide
          bigdaz Daz DeBoer added a comment - - edited

          Olivier Lamy I'm working to make Gradle Enterprise compatible with the Maven job type in Jenkins. GE for Maven is implemented as a Maven Extension, and our customers currently have to migrate away from using the `maven-plugin` to benefit from caching and build scans.

          Do you have any hints/advice on where I would start to make Maven detect and load extensions declared in the project `.mvn` directory? 

          I added `-Dmaven.multiModuleProjectDirectory=...` and `-Dmaven.projectBasedir=...` to the invocation, but that didn't seem to help. 

          Show
          bigdaz Daz DeBoer added a comment - - edited Olivier Lamy I'm working to make  Gradle Enterprise  compatible with the Maven job type in Jenkins. GE for Maven is implemented as a Maven Extension, and our customers currently have to migrate away from using the `maven-plugin` to benefit from caching and build scans. Do you have any hints/advice on where I would start to make Maven detect and load extensions declared in the project `.mvn` directory?  I added `-Dmaven.multiModuleProjectDirectory=...` and `-Dmaven.projectBasedir=...` to the invocation, but that didn't seem to help. 
          Hide
          bigdaz Daz DeBoer added a comment -

          Further to this, if the Gradle Enterprise Maven extension is added to `lib/ext` in the Maven installation, we get a little further using the Maven job type. In this case, the extension appears to be loaded multiple times, which causes failures in our extension.

          So unfortunately asking users to apply the extension directly doesn't help.

          Show
          bigdaz Daz DeBoer added a comment - Further to this, if the Gradle Enterprise Maven extension is added to `lib/ext` in the Maven installation, we get a little further using the Maven job type. In this case, the extension appears to be loaded multiple times, which causes failures in our extension. So unfortunately asking users to apply the extension directly doesn't help.

            People

            • Assignee:
              Unassigned
              Reporter:
              mcfoggy Matthieu Brouillard
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: