[MDEPLOY-116] uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Component/s: deploy:deploy
• Labels: scrub-review-started
• Environment: Maven 2.2.1. maven deploy plugin version not specified in pom.xml.
• Assignee: Robert Scholte
• Reporter: Bob Fields
• Created: 04/Feb/10 16:19
• Updated: 13/Sep/13 15:39
• Resolved: 13/Sep/13 15:39

Description

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.