Deploy plugin does not consider artifact type when deploying snapshots
----------------------------------------------------------------------
Key: MDEPLOY-43
URL: http://jira.codehaus.org/browse/MDEPLOY-43
Project: Maven 2.x Deploy Plugin
Issue Type: Bug
Affects Versions: 2.2.1
Environment: all environments
Reporter: Brill Pappin
Priority: Critical
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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
