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

Hudson deploy artifact does not use alternate settings.xml

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None
    • Platform: PC, OS: Linux

      The Hudson 'Deploy artifacts to Maven repository' does not take the settings.xml
      into account (also see bug #). This means that the local-repository in ~/.m2
      will be used which was not used during the build.

          [JENKINS-4939] Hudson deploy artifact does not use alternate settings.xml

          pleursoft created issue -
          pleursoft made changes -
          Link New: This issue depends on JENKINS-4938 [ JENKINS-4938 ]
          mdonohue made changes -
          Link New: This issue depends on JENKINS-4693 [ JENKINS-4693 ]
          mdonohue made changes -
          Link Original: This issue depends on JENKINS-4938 [ JENKINS-4938 ]
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-5628 [ JENKINS-5628 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135012 ] New: JNJira + In-Review [ 203207 ]

            Unassigned Unassigned
            pleursoft pleursoft
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: