Maven 2.x and 3.x Deploy Plugin

uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml correctly

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: deploy:deploy
  • Environment:
    Maven 2.2.1. maven deploy plugin version not specified in pom.xml.
  • Number of attachments :
    0

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.

Activity

Hide
Stephen Connolly added a comment -

Given that Maven 3 no longer supports uniqueVersion=false I am not sure that this issue is relevant any more

Show
Stephen Connolly added a comment - Given that Maven 3 no longer supports uniqueVersion=false I am not sure that this issue is relevant any more

People

Vote (2)
Watch (1)

Dates

  • Created:
    Updated: