You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/08/22 11:55:32 UTC

[jira] Commented: (MDEPLOY-116) uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml correctly

    [ https://jira.codehaus.org/browse/MDEPLOY-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276668#comment-276668 ] 

Stephen Connolly commented on MDEPLOY-116:
------------------------------------------

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

> uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml correctly
> --------------------------------------------------------------------------------------
>
>                 Key: MDEPLOY-116
>                 URL: https://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
>              Labels: scrub-review-started
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira