Maven Deploy Plugin
  1. Maven Deploy Plugin
  2. MDEPLOY-43

Deploy plugin does not consider artifact type when deploying snapshots

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Duplicate
    • Affects Version/s: 2.2.1
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      all environments

      Description

      A single artifact with multiple components is not handled properly.

      Deploying a single snapshot artifact that has multiple components such as a native component with an so/dll file and a matching lib file results in two different id's while only the last id is recorded in the meta data.

      Of course, this means that the first file can not be resolve.

      The deploy plugin should take the file type into account when deploying the artifact so that multiple components of an artifact have the same snapshot id.

      To test the issue, use the native-maven-plugin (http://mojo.codehaus.org/maven-native/native-maven-plugin/index.html) to deploy an artifact as a snapshot version.
      Once deployed inspect the repository; You should find an so/dll and a lib with two different snapshot ids and the maven-metadata.xml will contain the id of the last file that was actually copied (in this case the lib file).

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Brill Pappin
            • Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development