You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Max Schaefer (JIRA)" <ji...@codehaus.org> on 2010/02/17 08:31:55 UTC
[jira] Created: (MRELEASE-524) command line versions don't seem to
work on release:branch for specific format
command line versions don't seem to work on release:branch for specific format
--------------------------------------------------------------------------------
Key: MRELEASE-524
URL: http://jira.codehaus.org/browse/MRELEASE-524
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: branch
Affects Versions: 2.0
Environment: maven 2.2.1
Reporter: Max Schaefer
I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
E.g. this command taken from the documentation does not work.
mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
release:prepare supports this specific format for setting these values at command line.
Setting these values in a release.properties file e.g.
project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
project.rel.org.myCompany\:projectA=1.2
works also fine.
Specifying the default at commandline works also e.g.
mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
-DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Christoph Kutzinski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239986#action_239986 ]
Christoph Kutzinski commented on MRELEASE-524:
----------------------------------------------
BTW: is it also possible to specify the versions in a release.properties file or can they only be passed as command line parameters?
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Assignee: Brett Porter
> Fix For: 2.1
>
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem to
work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-524:
---------------------------------------
Attachment: MRELEASE-524-batch-mode(2).patch
Updated patch from http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/tree/MRELEASE-524-batch-mode
There were some runtime assertions causing test errors only when I ran the maven commandline. In IDEA the tests ran all fine.
Those assertions were never really necessary - I seem to be the first one. No tests covering them either.
http://github.com/lcorneliussen/maven-release/commit/66e5981dd944c6931face5a86a5862c1c0c73923
[MRELEASE-524] removed two runtime assertions that overeagerly tried to protect the ReleaseDescripto [more...]
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231443#action_231443 ]
Lars Corneliussen commented on MRELEASE-524:
--------------------------------------------
I created a new patch and also included test cases.
http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/commits/MRELEASE-524-batch-mode
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Max Schaefer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224623#action_224623 ]
Max Schaefer commented on MRELEASE-524:
---------------------------------------
Seems not to work :-(
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Christoph Kutzinski (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239985#action_239985 ]
Christoph Kutzinski commented on MRELEASE-524:
----------------------------------------------
Thanks, seems to work now.
However, the documentation on http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html is a little bit misleading as it doesn't mention the updateBranchVersions parameter which you have to use. Otherwise the .rel parameters will have no effect.
I.e.
mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
should read:
mvn --batch-mode release:branch -DupdateBranchVersions=true -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
-Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Assignee: Brett Porter
> Fix For: 2.1
>
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem to
work on release:branch for specific format
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRELEASE-524:
----------------------------------
Patch Submitted: [Yes]
Fix Version/s: 2.1
patch to review
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Fix For: 2.1
>
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236799#action_236799 ]
Brett Porter commented on MRELEASE-524:
---------------------------------------
I applied the patch, which went cleanly and made some improvement.
However, the command line versions still don't work - owing to no registration of the properties in the release:branch goal. I'll look at adding that.
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Fix For: 2.1
>
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230828#action_230828 ]
Lars Corneliussen commented on MRELEASE-524:
--------------------------------------------
What doesn't work? The patch or the changes? Any error?
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224529#action_224529 ]
Lars Corneliussen commented on MRELEASE-524:
--------------------------------------------
helo? :-)
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem to
work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-524:
---------------------------------------
Attachment: MRELEASE-524-batch-mode.patch
Based on r983489 in https://svn.apache.org/repos/asf/maven/release/trunk
Included commits:
- [MRELEASE-524] Added test cases (by Lars Corneliussen<me...@lcorneliussen.de> on 09.08.2010 12:05:12)
- [MRELEASE-524] command line versions don't seem to work on release:branch for specific format\n\no In interactive mode, the user was allways asked. Now he is only asked when the user did not specify versions explicitely. The fallback-suggestions on errors now are 1.0 for release, and 1.1-SNAPSHOT for development version. (by Lars Corneliussen<me...@lcorneliussen.de> on 05.05.2010 15:13:27)
View changes online: http://github.com/lcorneliussen/maven-release/compare/473197249e1caf39ee2cee6d0efc8a288c30d0c3...2e99512130cf7c224b9c9fcedfef0b96448d1934
# created from http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/maven-release/commits/MRELEASE-524-batch-mode
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Attachments: MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem
to work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220013#action_220013 ]
Lars Corneliussen commented on MRELEASE-524:
--------------------------------------------
I wrote a fix. Let me know if this is good enough.. then I write some tests and submit a patch:
http://github.com/lcorneliussen/maven-release/commit/27df9d38c7f52b3752bebfb24f433368097cd090
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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] Issue Comment Edited: (MRELEASE-524) command line versions
don't seem to work on release:branch for specific format
Posted by "Lars Corneliussen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220013#action_220013 ]
Lars Corneliussen edited comment on MRELEASE-524 at 5/5/10 8:23 AM:
--------------------------------------------------------------------
I wrote a fix. Let me know if this is good enough.. then I write some tests and submit a patch:
http://github.com/lcorneliussen/maven-release/commit/ffa24c5b98435bd8844e46a1130262051a88368f
was (Author: lcorneliussen):
I wrote a fix. Let me know if this is good enough.. then I write some tests and submit a patch:
http://github.com/lcorneliussen/maven-release/commit/27df9d38c7f52b3752bebfb24f433368097cd090
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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-524) command line versions don't seem to
work on release:branch for specific format
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-524.
---------------------------------
Resolution: Fixed
Assignee: Brett Porter
final issue resolved in r1002513.
Please take a look and see if this is what you were after
> command line versions don't seem to work on release:branch for specific format
> --------------------------------------------------------------------------------
>
> Key: MRELEASE-524
> URL: http://jira.codehaus.org/browse/MRELEASE-524
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0
> Environment: maven 2.2.1
> Reporter: Max Schaefer
> Assignee: Brett Porter
> Fix For: 2.1
>
> Attachments: MRELEASE-524-batch-mode(2).patch, MRELEASE-524-batch-mode.patch
>
>
> I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode.
> E.g. this command taken from the documentation does not work.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \
> -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT
> release:prepare supports this specific format for setting these values at command line.
> Setting these values in a release.properties file e.g.
> project.dev.org.myCompany\:projectA=2.0-SNAPSHOT
> project.rel.org.myCompany\:projectA=1.2
> works also fine.
> Specifying the default at commandline works also e.g.
> mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \
> -DdevelopmentVersion=2.0-SNAPSHOT
--
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