[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301960#comment-301960 ] Manuel AUGUSTO commented on MRELEASE-679: - Hello, I had the same problem and i resolved i

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301661#comment-301661 ] Robert Scholte commented on MRELEASE-679: - @Adrian, I'd like to know in which version it

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301617#comment-301617 ] Adrian Pillinger commented on MRELEASE-679: --- I've just experienced this same issue. Whe

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297140#comment-297140 ] Robert Scholte commented on MRELEASE-679: - I know this works for the http-protocol, so my

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297118#comment-297118 ] Vedavyas Panneershelvam commented on MRELEASE-679: -- Robert, The content of t

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297063#comment-297063 ] Robert Scholte commented on MRELEASE-679: - Vedavyas, Does the pom.xml from which you try

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam edited comment on MRELEASE-679 at 4/23/12 9:07 AM:

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam edited comment on MRELEASE-679 at 4/23/12 9:03 AM:

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam commented on MRELEASE-679: -- Using Maven version 3.0.3 an

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291884#comment-291884 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:55 AM: - When I use mave

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:54 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291884#comment-291884 ] Frans commented on MRELEASE-679: When I use maven-release-plugin:2.1, the behavior changes: |conn

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:43 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans edited comment on MRELEASE-679 at 2/16/12 4:41 AM: - Same issue. Mav

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882 ] Frans commented on MRELEASE-679: Same issue. Maven-release-plugin:2.0, Subversion, multi-module p