You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Franck HUGOT (JIRA)" <ji...@codehaus.org> on 2007/09/05 15:32:11 UTC
[jira] Created: (MRELEASE-281) Pom version is not modified during
release:branch goal
Pom version is not modified during release:branch goal
------------------------------------------------------
Key: MRELEASE-281
URL: http://jira.codehaus.org/browse/MRELEASE-281
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-6
Environment: maven 2.0.6
Reporter: Franck HUGOT
When I perform release:branch I have 3 problems :
- FirstI have to specify the branch name on the command line (I don't want to have it in my pom to commit it!), why it don't ask me for the branche name as for the release:prepare goal?
- Secondly, the most important, the version in the pom (<version></version>) is not modified. It should also work as the release:prepare goal.
- To finish, the documentation on the web site talks about tag, I think you should talk about branch (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html)
I think this goal (release:branch) should have the same behavior as the release:prepare because the same actions have to be performed.
--
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-281) Pom version is not modified during
release:branch goal
Posted by "Martin Vysny (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134378#action_134378 ]
Martin Vysny commented on MRELEASE-281:
---------------------------------------
This behaviour can be observed when the release plugin is configured by parent pom. It then ignores command-line arguments completely.
> Pom version is not modified during release:branch goal
> ------------------------------------------------------
>
> Key: MRELEASE-281
> URL: http://jira.codehaus.org/browse/MRELEASE-281
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Environment: maven 2.0.6
> Reporter: Franck HUGOT
>
> When I perform release:branch I have 3 problems :
> - FirstI have to specify the branch name on the command line (I don't want to have it in my pom to commit it!), why it don't ask me for the branche name as for the release:prepare goal?
> - Secondly, the most important, the version in the pom (<version></version>) is not modified. It should also work as the release:prepare goal.
> - To finish, the documentation on the web site talks about tag, I think you should talk about branch (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html)
> I think this goal (release:branch) should have the same behavior as the release:prepare because the same actions have to be performed.
--
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-281) Pom version is not modified during
release:branch goal
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-281:
-------------------------------------
Component/s: prepare
> Pom version is not modified during release:branch goal
> ------------------------------------------------------
>
> Key: MRELEASE-281
> URL: http://jira.codehaus.org/browse/MRELEASE-281
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-6
> Environment: maven 2.0.6
> Reporter: Franck HUGOT
>
> When I perform release:branch I have 3 problems :
> - FirstI have to specify the branch name on the command line (I don't want to have it in my pom to commit it!), why it don't ask me for the branche name as for the release:prepare goal?
> - Secondly, the most important, the version in the pom (<version></version>) is not modified. It should also work as the release:prepare goal.
> - To finish, the documentation on the web site talks about tag, I think you should talk about branch (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html)
> I think this goal (release:branch) should have the same behavior as the release:prepare because the same actions have to be performed.
--
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] (MRELEASE-281) Pom version is not modified during
release:branch goal
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-281:
------------------------------------
Component/s: (was: prepare)
branch
> Pom version is not modified during release:branch goal
> ------------------------------------------------------
>
> Key: MRELEASE-281
> URL: https://jira.codehaus.org/browse/MRELEASE-281
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0-beta-6
> Environment: maven 2.0.6
> Reporter: Franck HUGOT
>
> When I perform release:branch I have 3 problems :
> - FirstI have to specify the branch name on the command line (I don't want to have it in my pom to commit it!), why it don't ask me for the branche name as for the release:prepare goal?
> - Secondly, the most important, the version in the pom (<version></version>) is not modified. It should also work as the release:prepare goal.
> - To finish, the documentation on the web site talks about tag, I think you should talk about branch (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html)
> I think this goal (release:branch) should have the same behavior as the release:prepare because the same actions have to be performed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-281) Pom version is not modified during
release:branch goal
Posted by "Martin Vysny (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134376#action_134376 ]
Martin Vysny commented on MRELEASE-281:
---------------------------------------
I can confirm that with Maven 2.0.9 and Release plugin 2.0-beta-7 the updateWorkingCopyVersions argument does nothing. The plugin always behaves as if -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false - it never updates trunk pom.xml versions.
> Pom version is not modified during release:branch goal
> ------------------------------------------------------
>
> Key: MRELEASE-281
> URL: http://jira.codehaus.org/browse/MRELEASE-281
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-6
> Environment: maven 2.0.6
> Reporter: Franck HUGOT
>
> When I perform release:branch I have 3 problems :
> - FirstI have to specify the branch name on the command line (I don't want to have it in my pom to commit it!), why it don't ask me for the branche name as for the release:prepare goal?
> - Secondly, the most important, the version in the pom (<version></version>) is not modified. It should also work as the release:prepare goal.
> - To finish, the documentation on the web site talks about tag, I think you should talk about branch (http://maven.apache.org/plugins/maven-release-plugin/examples/branch.html)
> I think this goal (release:branch) should have the same behavior as the release:prepare because the same actions have to be performed.
--
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