[
http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
