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

Different unique versions assigned to additional attached artifacts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • deploy-plugin
    • None
    • Platform: All, OS: All

      When enabling deployment with the 'assign unique versions' flag enabled on a
      Maven project which has additional artifacts attached (e.g. sources or javadocs
      jars), the deployer creates another unique version for the additional artifacts
      then the one used for the main artifact.

      The Maven metadata will also point to the unique version for the additional
      artifact, causing the main artifact to be unavailable as a SNAPSHOT to Maven.

          [JENKINS-3518] Different unique versions assigned to additional attached artifacts

          gertvanthienen created issue -

          tjuerge added a comment -

          marking as duplicate of #2593

              • This issue has been marked as a duplicate of 2593 ***

          tjuerge added a comment - marking as duplicate of #2593 This issue has been marked as a duplicate of 2593 ***
          tjuerge made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          tjuerge made changes -
          Link New: This issue duplicates JENKINS-2593 [ JENKINS-2593 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 133591 ] New: JNJira + In-Review [ 202273 ]

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

              Created:
              Updated:
              Resolved: