[
https://issues.apache.org/jira/browse/MDEPLOY-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965727#comment-17965727
]
Olivier Lamy commented on MDEPLOY-153:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#462|https://github.com/apache/maven-deploy-plugin/issues/462].
> Improper unique version handling
> --------------------------------
>
> Key: MDEPLOY-153
> URL: https://issues.apache.org/jira/browse/MDEPLOY-153
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: Windows 7, 64-bit, Java 7u5, Maven 3.0.4
> Reporter: Krisztian Kocsis
> Assignee: Robert Scholte
> Priority: Major
>
> Even if I set: <uniqueVersion>false</uniqueVersion>, it uploads unique
> versioned artifacts:
> Uploading:
> http://optimaster.eu:8082/archiva/repository/mai/eu/optimaster/mai/mai-application/1.0.0-alpha2-SNAPSHOT/mai-application-1.0.0-alpha2-20120813.143737-3.jar
> Another problem is that if I use 'true' for uniqueVersion the uploaded child
> module POMs reference the parent POM as {{<name>\-x.x.x-SNAPSHOT}} but it is
> also uploaded as {{<parent>\-x.x.x-<unique>.pom}} hence the repository
> manager (Apache Archiva) does not find it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
