[jira] Commented: (MRELEASE-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154950#action_154950 ] jcrouvi commented on MRELEASE-173: -- Hi, Is this bug really closed: * Test environment ** Maven version: 2.0.9 ** Java version: 1.6.0_07 ** OS name: windows xp version: 5.1 arch: x86 Family: windows ** maven-release-plugin = 2.0-beta-8 ** SCM = CVS * Maven command: ** mvn -B clean release:clean release:prepare release:perform \ -Dmaven.test.failure.ignore=false \ -Dtag=TEST_RELEASE-1_0_13 \ -DreleaseVersion=1.0.13 \ -DdevelopmentVersion=2.0.0-SNAPSHOT * Expected output in pom.xml: ** version2.0.0-SNAPSHOT/version * Effective output in pom.xml: ** version1.0.14-SNAPSHOT/version WRONG Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154953#action_154953 ] Arnaud Heritier commented on MRELEASE-173: -- it should but there's perhaps a bug. Can you open another issue please ? Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154963#action_154963 ] jcrouvi commented on MRELEASE-173: -- Issue http://jira.codehaus.org/browse/MRELEASE-389 opened Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152192#action_152192 ] Joshua Pollak commented on MRELEASE-173: Does this feature apply to the branch goal as well? I'd like to be able to do: mvn release:branch -DbranchVersion=1.2-myFeature -DbranchName=myFeature Can 2.0-beta-8 be released so we can start testing this feature? Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152052#action_152052 ] James Lorenzen commented on MRELEASE-173: - It would be really great if v 2.0-beta-8 could get released so I could use this feature. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=132543#action_132543 ] Paul Gier commented on MRELEASE-173: I added the command line parameters releaseVersion and developmentVersion. These will override the automatic versioning. For multi-module projects you can also use the project.rel.groupId:artifactId format which will take priority for the specific module that it applies to. The changes are in svn so you can check it out and try it locally. If this fix seems ok, I'll close the issue and upload a new snapshot. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131811#action_131811 ] Paul Gier commented on MRELEASE-173: I took a different approach than what was in the patch, since the patch was out of date and only handled single version releases. To set the release version from the command line, you now have to use project.rel or project.dev and the groupId and artifactId. So you end up with something like this: mvn --batch-mode -Dtag=my-proj-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \ -Dproject.dev.org.myCompany:projectA=1.3-SNAPSHOT release:prepare This allows multiple versions to be passed for a multi-module release. There is now an example for this in the site docs in svn. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131818#action_131818 ] Elias Ross commented on MRELEASE-173: - Requiring groupId and artifactId for the use case of single version releases just complicates writing scripts and using build tools. I'm against what Paul suggests, or at least I'm for a single-version solution. And honestly, I never understood the use case of releasing multiple artifacts with different versions, which just sounds like it would cause trouble. Have you seen any build tools that would support building a project with N different sub versions? There's now 17 votes for this trivial feature and so I wonder why nobody's taken it on... Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131823#action_131823 ] Paul Gier commented on MRELEASE-173: Ok, I could add releaseVersion and devVersion as default versions which can be overridden by the more specific properties which include the groupId and artifactId. But being able to release a multi-module project with multiple versions is an important feature IMO. We currently have a project set up like that, so handling only single version releases would not help me. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Assignee: Paul Gier Fix For: 2.0-beta-8 Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115300 ] Santhosh Kumar commented on MRELEASE-173: - Adding these two command line parameters greatly simplifies the integration of maven into the automated build tools. I would assume these two parameters behave this way. 1. If releaseVersion is specified, it would override the current pom.xml version. If running in interactive mode, this version would be used as default answer. 2. If devVersion is specified, -SNAPSHOT would be suffixed and used as new dev version. If running in interactive mode, it would be used as default answer. If devVersion is not specified, then version computed from step 1 would be incremented by one (with -SNAPSHOT) and used. We have modified the release plugin 2.4-alpha4 version in our internal environment to have this feature. I can post the diff file if it helps. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113321 ] Elias Ross commented on MRELEASE-173: - I'm 100% for this patch. All our builds are automated by Quickbuild and it is ridiculous to have to pipe in input from a file to supply the versioning information. Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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-173) Allow command line specification of versions
[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111083 ] Marc-Andre Houle commented on MRELEASE-173: --- I would really appreciate this feature. For many building system, that can be very neat because you don't always have the possibility to enter the version number. Does the developpers need some help or whatever? Since I need it, I'm ready to try helping implementing this feature to include it in next releases. Is there lot of thing missing than this diff file? Marc Allow command line specification of versions Key: MRELEASE-173 URL: http://jira.codehaus.org/browse/MRELEASE-173 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-3, 2.0-beta-4, 2.0-beta-5 Reporter: Chris Tucker Attachments: release-version.diff It is convenient in a batchMode environment to specify the version to release and the new version to update SNAPSHOT artifacts to. The attached patch against maven-release-manager and maven-release-plugin provides the basic functionality to allow this. The maven-release-plugin will now accept two new arguments: -DreleaseVersion=version string for release -DdevVersion=version string for next development cycle For example, to release version 1.2 of a project and move up to version 2.0-SNAPSHOT one would issue: $ mvn release:clean release:prepare -DreleaseVersion=1.2 -DdevVersion=2.0 --batch-mode This patch is against current trunk (471862). It currently doesn't support resuming, so a release:clean is necessary if a previous release attempt has been prepared. -- 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
