maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MRELEASE-600) command line versions don't work as documented on release:branch
Date Wed, 29 Sep 2010 15:10:32 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed MRELEASE-600.
---------------------------------

    Resolution: Duplicate
      Assignee: Brett Porter

this is fixed in trunk now

> command line versions don't work as documented on release:branch
> ----------------------------------------------------------------
>
>                 Key: MRELEASE-600
>                 URL: http://jira.codehaus.org/browse/MRELEASE-600
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.0
>            Reporter: Christoph Kutzinski
>            Assignee: Brett Porter
>
> In the documentation of the release plugin it is written that you can specify the versions
via command line properties a la
> -Dproject.rel.groupId:artifactId=1.2.3 and so on
> (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html )
> According to MRELEASE-387 this should be working as of maven-release-plugin 2.0
> However it is only working with the newly introduced parameters 'developmentVersion'
and 'releaseVersion' (which obviously cannot be specified per submodule as I need it).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message