maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] (MDEPLOY-153) Improper unique version handling
Date Thu, 12 Sep 2013 20:53:52 GMT


Robert Scholte closed MDEPLOY-153.

    Resolution: Not A Bug
      Assignee: Robert Scholte

The behavior has changed since Maven3
> Improper unique version handling
> --------------------------------
>                 Key: MDEPLOY-153
>                 URL:
>             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
> Uploading:
> 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:

View raw message