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

Maven 2 Extra Steps does not use private Maven repository if set on project

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      If "Use private Maven repository" is set for maven build, then it should also be
      set for any configured M2 Extra Build Steps.

      Currently, the flags passed to the main mvn task to use the private repository
      i.e.:
      Executing Maven: -B -f /opt/hudson/.hudson/jobs/MYJOB/workspace/pom.xml
      -Dmaven.repo.local=/opt/hudson/.hudson/jobs/MYJOB/workspace/.repository package

      are not passed to the maven that is invoked from any of these extra build steps.
      i.e.:
      [workspace] $ /opt/apache-maven-2.0.9/bin/mvn clean

        Attachments

          Activity

          jchristi jchristi created issue -
          abayer Andrew Bayer made changes -
          Field Original Value New Value
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Resolved [ 5 ]
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          radaczynski radaczynski made changes -
          Resolution Won't Fix [ 2 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 134102 ] JNJira + In-Review [ 185922 ]
          abayer Andrew Bayer made changes -
          Assignee Andrew Bayer [ abayer ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jchristi jchristi
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: