[jira] Commented: (MRELEASE-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=208821#action_208821 ] werner mueller commented on MRELEASE-427: - an issue related to branching was created: MRELEASE-514 Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171732#action_171732 ] Pablo commented on MRELEASE-427: I have the same problem when executing mvn release:branch. It would be useful to add the -DremoteTagging argument also when making branches. Thank you. Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=171735#action_171735 ] Olivier Lamy commented on MRELEASE-427: --- please create a new issue! Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169940#action_169940 ] Olivier Lamy commented on MRELEASE-427: --- this make sense. Others ? Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169939#action_169939 ] Benjamin Bentmann commented on MRELEASE-427: One of Maven's goals is to support convention over configuration. In this sense, wouldn't it be better if we made remoteTagging=true the default? I mean if the default configuration does simply not work reliably with Subversion 1.5.0, what's the default good for then? Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169977#action_169977 ] Olivier Lamy commented on MRELEASE-427: --- reopen to have comments on : true/false which one must be the default value ? Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169993#action_169993 ] Clint Gilbert commented on MRELEASE-427: Does remoteTagging=true work with Subversion 1.4.x? If so, remoteTagging=true should be the default,. since it works with all svn versions. Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0)
[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169994#action_169994 ] Olivier Lamy commented on MRELEASE-427: --- yes it works with 1.4.x. I have tested the following : * cygwin svn 1.4.6 and 1.5.1 * solaris svn 1.4.6 and 1.5.4 Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn 1.5.0) -- Key: MRELEASE-427 URL: http://jira.codehaus.org/browse/MRELEASE-427 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0-beta-8 Environment: svn version 1.5.0 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Critical Fix For: 2.0-beta-9 Due to an issue with svn 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround. -- 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
