maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Kutzinski (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-387) command line versions don't seem to work on release:branch
Date Fri, 24 Sep 2010 15:38:33 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236377#action_236377
] 

Christoph Kutzinski commented on MRELEASE-387:
----------------------------------------------

This is still not working as described in the documentation (-Dproject.rel.org.myCompany:projectA=1.2
\
-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT), only the newly intorduced properties work.

> command line versions don't seem to work on release:branch
> ----------------------------------------------------------
>
>                 Key: MRELEASE-387
>                 URL: http://jira.codehaus.org/browse/MRELEASE-387
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: branch
>    Affects Versions: 2.0-beta-8
>         Environment: maven 2.0.9 and 2.1.0 M1, maven release plugin 2.0-beta-8
>            Reporter: Jeff Vogelsang
>            Assignee: Olivier Lamy
>             Fix For: 2.0
>
>         Attachments: addSupportForVersion.patch
>
>
> I have tried all the various permutations for passing versions to the command line while
making a branch. The plugin ignores my parameters when running release:branch. It either interactively
prompts for new versions, or injects the defaults if I pass parameters in batch mode.
> Here's an example of two commands I have tried running that don't work:
> mvn release:branch -DbranchName=RB-[top-level-project-name]-1.0.4 -DautoVersionSubmodules=true
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DdevelopmentVersion=1.0.4-SNAPSHOT
> mvn release:branch -DbranchName=RB-[top-level-project-name]-1.0.4 -DautoVersionSubmodules=true
-DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -Dproject.dev.[org package].[top-level-project-name]=1.0.4-SNAPSHOT
> Both of those commands prompt me for versions and no matter what parameters I type use
the current project revision as the default. If I do batch mode with --batch or -B, the release
plugin just injects the current project revision into the branch and ignores my parameters.

-- 
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