[ 
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157601#action_157601
 ] 

Clint Gilbert commented on SCM-406:
-----------------------------------

It makes sense to tag from the local copy, since that's the code that's just 
been compiled and tested.  Someone could have checked in a breaking change to 
the trunk which you wouldn't want in the release, for instance.

But how about this (I'm just brainstorming; I don't know enough about the SCM 
code to know how feasible this is)?

* release:prepare runs, updating poms, removing -SNAPSHOT from versions, etc.
* The release plugin checks in the updated poms.  If there's an error (the 
working copy is out of date, say), notify the user to update and re-try 
release:prepare
* The release plugin records the revision number of the commit
* The release plugin tags (via a remote URL) the recorded trunk revision as the 
release
* The release plugin updates the needed poms to new snapshot versions and 
checks them in.

I hope there's a fix for this soon; we're fine with SVN 1.4.x for now, but it 
would be much more convenient to be able to upgrade.

> scm tag does not work with Subversion 1.5.1
> -------------------------------------------
>
>                 Key: SCM-406
>                 URL: http://jira.codehaus.org/browse/SCM-406
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0
>            Reporter: James William Dumay
>             Fix For: 1.1.1
>
>
> scm:checkin does not work with Subversion 1.5.1
> On release:perform (which I assume calls scm:checkin) the following error 
> occurs:
> {code}
> svn: File 
> '/svn/private/atlassian/confluence/tags/confluence-project-2.10-m1/conf-acceptance-test/pom.xml'
>  already exists
> {code}
> Using subversion 1.4.x is a good enough 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

        

Reply via email to