[
https://issues.apache.org/jira/browse/MDEPLOY-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965683#comment-17965683
]
Olivier Lamy commented on MDEPLOY-116:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#330|https://github.com/apache/maven-deploy-plugin/issues/330].
> uniqueVersion=false does not update SNAPSHOT child module maven-metadata.xml
> correctly
> --------------------------------------------------------------------------------------
>
> Key: MDEPLOY-116
> URL: https://issues.apache.org/jira/browse/MDEPLOY-116
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Components: deploy:deploy
> Environment: Maven 2.2.1. maven deploy plugin version not specified
> in pom.xml.
> Reporter: Bob Fields
> Assignee: Robert Scholte
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
