You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/09/12 22:53:52 UTC

[jira] (MDEPLOY-153) Improper unique version handling

     [ https://jira.codehaus.org/browse/MDEPLOY-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MDEPLOY-153.
----------------------------------

    Resolution: Not A Bug
      Assignee: Robert Scholte

See https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
The behavior has changed since Maven3
                
> Improper unique version handling
> --------------------------------
>
>                 Key: MDEPLOY-153
>                 URL: https://jira.codehaus.org/browse/MDEPLOY-153
>             Project: Maven Deploy Plugin
>          Issue Type: Bug
>    Affects Versions: 2.7
>         Environment: Windows 7, 64-bit, Java 7u5, Maven 3.0.4
>            Reporter: Krisztian Kocsis
>            Assignee: Robert Scholte
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira