[jira] Commented: (MRELEASE-387) command line versions don't seem to work on release:branch

["pkernevez (JIRA)" <ji...@codehaus.org>]

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

pkernevez commented on MRELEASE-387:
------------------------------------

This is not a perfect patch:
The code does this things:
# It updates all pom to the next releaseVersion 
# It commits all modification of the version to the TRUNK
# it copy the trunk to the branches
# it updates all the pom with the developmentVersion
# it commit it to the trunk

I prefered that it doesn't commit the trunk (step 2) according to that this version hasn't to commited in the trunk. But it's not a big issue cause these modifications are rollbacked by the last step.

I ran it with this command 
{code}
mvn release:branch -Denv=prod -DbranchName=17.1 -DupdateBranchVersions=true 
 -DupdateWorkingCopyVersions=false  -DreleaseVersion=17.1-SNAPSHOT -DdevelopmentVersion=17.2-SNAPSHOT
{code}

> 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
>    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
>             Fix For: 2.0-beta-9
>
>         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