You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeff Vogelsang (JIRA)" <ji...@codehaus.org> on 2008/11/14 14:31:13 UTC
[jira] Created: (MRELEASE-387) command line versions don't seem to
work on release:branch
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
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
[jira] Updated: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MRELEASE-387:
-------------------------------
Fix Version/s: 2.0-beta-9
> 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
>
>
> 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
[jira] Commented: (MRELEASE-387) command line versions don't seem
to work on release:branch
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236800#action_236800 ]
Brett Porter commented on MRELEASE-387:
---------------------------------------
Christoph - I'm looking at this as part of MRELEASE-524 that raised it also
> 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
[jira] Updated: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-387:
-------------------------------------
Patch Submitted: [Yes]
> 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
> 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
[jira] Commented: (MRELEASE-387) command line versions don't seem
to work on release:branch
Posted by "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
[jira] Updated: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-387:
-------------------------------------
Component/s: branch
> 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
> 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
[jira] Commented: (MRELEASE-387) command line versions don't seem
to work on release:branch
Posted by "Ryan Senior (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162184#action_162184 ]
Ryan Senior commented on MRELEASE-387:
--------------------------------------
According to this: http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html the arguments required to set working and branch versions are: -Dproject.rel.org.myCompany:projectA=1.2 \
-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT . In looking at the patch above, it's adding new parameters rather than using project.rel and project.dev. Is that correct?
> 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
> 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
[jira] Commented: (MRELEASE-387) command line versions don't seem
to work on release:branch
Posted by "Thomas Marti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165960#action_165960 ]
Thomas Marti commented on MRELEASE-387:
---------------------------------------
Hi
We're desperately waiting for this patch...anyway to speed up its inclusion??
In response to Ryan Senior...I think we have to copy the following lines from {{PrepareReleaseMojo.java}} to {{BranchReleaseMojo.java}} as well:
{noformat}// Create a config containing values from the system properties (command line properties).
ReleaseDescriptor sysPropertiesConfig = ReleaseUtils.copyPropertiesToReleaseDescriptor( System.getProperties() );
mergeCommandLineConfig( config, sysPropertiesConfig );{noformat}
And obviously the {{mergeCommandLineConfig()}} method has to be made protected and moved up to {{AbstractReleaseMojo.java}}.
> 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
> 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
[jira] Commented: (MRELEASE-387) command line versions don't seem
to work on release:branch
Posted by "Christoph Kutzinski (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "pkernevez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
pkernevez updated MRELEASE-387:
-------------------------------
Attachment: addSupportForVersion.patch
PAtch for implementing this issue
> 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
[jira] Closed: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-387.
---------------------------------
Assignee: Olivier Lamy
Resolution: Fixed
fix in rev 798709.
Thanks !
> 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-beta-10
>
> 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
[jira] Updated: (MRELEASE-387) command line versions don't seem to
work on release:branch
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated MRELEASE-387:
----------------------------------
Fix Version/s: (was: 2.0-beta-9)
2.0-beta-10
> 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
> Fix For: 2.0-beta-10
>
> 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