uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml
correctly
--------------------------------------------------------------------------------------
Key: MDEPLOY-116
URL: http://jira.codehaus.org/browse/MDEPLOY-116
Project: Maven 2.x Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Environment: Maven 2.2.1. maven deploy plugin version not specified in
pom.xml.
Reporter: Bob Fields
Parent pom.xml has
<distributionManagement>
<repository>
<id>andromda-repository</id>
<name>AndroMDA Repository</name>
<url>file:/var/www/maven2</url>
</repository>
Child pom.xml files do not specify distribution repository. Parent and child
artifacts were deployed with maven-metadata.xml containing <versioning>
information. Later, <uniqueVersion>false</uniqueVersion> was added. The parent
maven-metadata.xml was updated correctly (no <versioning>) but the child
maven-metadata.xml had <lastUpdated> changed in the <versioning> section,
rather than simply deleting the section entirely, resulting in an old
timestamped version of the .pom file returned to the repository user. The only
workaround was to delete all of the project child artifacts in the repository
and deploy again.
--
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
