Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Duplicate
-
Affects Version/s: 2.2.1
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:all environments
-
Number of attachments :
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
- is related to
-
MNG-1021
Build numbers are incremented when they shouldn't
-
-
MDEPLOY-48
deploy:deploy-file does not support deploying sources jars too
-
We ran into this issue while trying to deploy several snapshot components (jar, source and others) from an external source to our local Maven repository. We have to run mvn deploy:deploy-file on each component and each time it runs the version number gets bumped. Only the last component can be reolved. One work-around is to specify -DuniqueVersion=false but this is not an acceptable solution in all cases.