[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=190485#action_190485
]
Stefan Sperling commented on SCM-406:
-
The underlying problem in Subversion has been fixed in 1.6.5.
See http://subversion.tigris.org/issues/show_bug.cgi?id=3119
and the 1.6.5 entry in http://svn.collab.net/repos/svn/trunk/CHANGES
Maybe the plugin should limit use of its workaround to affected versions only?
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
Assignee: Olivier Lamy
Fix For: 1.2
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169706#action_169706
]
Olivier Lamy commented on SCM-406:
--
see proposals added in SCM-262. This will need some changes in release
plugin/manager too as the proposal won't be activated by default in order to
preserve backward compatibility.
I hope I will find some friends to test the fix :D (I prefer to call this a
workaround to a svn issue !)
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
Assignee: Olivier Lamy
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=169447#action_169447
]
Stephen Connolly commented on SCM-406:
--
There are some reports I saw a month back on the subversion mailing list that
this is an issue with the neon transport. If you use the serf transport the
problem goes away.
AFAIK the situation is as follows:
svn:// always works
svn+ssh:// always works
http:// only works with serf (I have not confirmed this yet)
https:// only works with serf (I have not confirmed this yet)
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=167681#action_167681
]
Johan van Ee commented on SCM-406:
--
Is there any news when this bug will be fixed in subversion?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=166999#action_166999
]
Justin Edelson commented on SCM-406:
Has anyone tested this against Subversion 1.6 RC2?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162018#action_162018
]
Martin Nilsson commented on SCM-406:
I have experienced the same problem, but after changing the protocol from http
to svn (i.e. using svnserve instead of apache) I managed to release without the
error.
I'm using svn 1.5.5
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160665#action_160665
]
Dan Tran commented on SCM-406:
--
From last view comments, the fix will be at SVN side. The bug will be moved
out of 1.1.1 release and probably will not get fixed since we do have work
around
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160425#action_160425
]
Brent Plump commented on SCM-406:
-
The core subversion issue is tracked here:
http://subversion.tigris.org/issues/show_bug.cgi?id=3119 Daniel Shahaf's
comment (posted on December 31) links to a good summary of the issue.
Unless the release/scm plugins implement a workaround, we'll need to wait for
this issue to be fixed by the svn team.
In the meantime, I am using svn 1.5.0 for release actions and the current
version for the rest of my work.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157678#action_157678
]
Kuno Baeriswyl commented on SCM-406:
I've contacted the subversion developer list. Nobody of the subversion team
seams to be aware of this problem...as a consequence, the issue won't get
fixed...
Can anybody reproduce the problem with subversion? Or does anybody know exactly
what does not work with subversion?
If so, please report it the topic in the developer list :
http://www.nabble.com/Maven-scm-tag-does-not-work-with-Subversion-1.5.x-td20930592.html
THanks a lot. I hope we can fixed it this way.
Kuno
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157592#action_157592
]
George Gastaldi commented on SCM-406:
-
Al,
You may upgrade your server to svn 1.5, and use svn client 1.5.0 (download link
in previous comments). This is what I am using now.
Regards,
George Gastaldi
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157593#action_157593
]
Kent Lam commented on SCM-406:
--
I made a bat file to do the release, this is what i do in the script until this
problem is fixed:
echo Preparing the release...
call mvn release:clean release:prepare -Darguments=-Pproduction
if %ERRORLEVEL% NEQ 0 goto retry
:retry
echo !!! Failure could be due to SVN 1.5 problem of tagging
http://jira.codehaus.org/browse/SCM-406, Going to update, then retry mvn
release:prepare!!!
svn up
call mvn release:prepare -Darguments=-Pproduction
if %ERRORLEVEL% NEQ 0 goto failed
goto preparesuccess
:preparesuccess
echo *** Please confirm that the Prepare was successful!
echo *** Ctrl-C if the Prepare was NOT successful.
pause
:failed
cd
echo !!! Failed to release! Please fix issues and rerun script.
goto finished
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157599#action_157599
]
Clint Gilbert commented on SCM-406:
---
George,
I've heard that there are some major problems with SVN 1.5.0 that are fixed
with later releases, potentially making 1.5.0 a bad option.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157410#action_157410
]
Kuno Baeriswyl commented on SCM-406:
[Using subversion 1.5.0 is also a good workaround for the moment. ]
Unfortunately, it isn't. Generally, this version is not recommended for
productive use. And I've got other show stoppers using this version.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157411#action_157411
]
Johannes Schneider commented on SCM-406:
Please fix this! It has been reported a few months ago and is a *real* show
stopper.
Most of the people out there use Subversion - and nearly everyone has to
release a piece of software somewhen...
I really wait for some competition for Maven
Sorry for ranting - but sometimes it is necessary...
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155882#action_155882
]
Yann Albou commented on SCM-406:
Why not using the SVN lock and then release lock when the tag is done ?
By doing this we will prevent others to commit changes during the tag.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155590#action_155590
]
Torsten Juergeleit commented on SCM-406:
Creating a copy (tag) on a working directory after performing a commit with SVN
1.5.1-1.5.4 seems to be an SVN issue
http://subversion.tigris.org/servlets/BrowseList?list=usersby=threadfrom=686753
How about implementing the code change (using cl.createArgument().setValue(
repository.getUrl() ); instead of cl.createArgument().setValue( . ); )
suggested by Kyle Lebel?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155597#action_155597
]
George Gastaldi commented on SCM-406:
-
Torsten,
If applied that patch, you could not solve the worst scenario: others may
commit on trunk, so the tag created could not really be the one that you
checked out and ran tests/packaged locally.
What do you guys think about it ?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155632#action_155632
]
Torsten Juergeleit commented on SCM-406:
George,
you're right. Hard-coding the update to trunk like the patch in SCM-262 doesn't
fly.
So how about the workaround suggested by Alison Winters to do svn update
prior to the svn copy in ScmTagPhase?
Maybe something like
{code}
Index: src/main/java/org/apache/maven/shared/release/phase/ScmTagPhase.java
===
--- src/main/java/org/apache/maven/shared/release/phase/ScmTagPhase.java
(revision 720901)
+++ src/main/java/org/apache/maven/shared/release/phase/ScmTagPhase.java
(working copy)
@@ -61,8 +61,6 @@
validateConfiguration( releaseDescriptor );
-logInfo( relResult, Tagging release with the label +
releaseDescriptor.getScmReleaseLabel() + ... );
-
ScmRepository repository;
ScmProvider provider;
try
@@ -80,12 +78,35 @@
throw new ReleaseExecutionException( Unable to configure SCM
repository: + e.getMessage(), e );
}
+ // TODO: want includes/excludes?
+ScmFileSet fileSet = new ScmFileSet( new File(
releaseDescriptor.getWorkingDirectory() ) );
+
+// Due to a Subversion bug
http://subversion.tigris.org/servlets/BrowseList?list=usersby=threadfrom=686753
+// regarding the tag command (svn copy) we need to update the working
directory first!
+if (svn.equals(provider.getScmType()))
+{
+ UpdateScmResult result;
+ try
+ {
+ logInfo( relResult, Due to a Subversion bug we have to update
the working directory before tagging ... );
+ result = provider.update( repository, fileSet );
+ }
+ catch ( ScmException e )
+ {
+ throw new ReleaseExecutionException( An error is occurred
while updating working directory: + e.getMessage(), e );
+ }
+
+ if ( !result.isSuccess() )
+ {
+ throw new ReleaseScmCommandException( Unable to update
working directory, result );
+ }
+}
+
TagScmResult result;
try
{
-// TODO: want includes/excludes?
-ScmFileSet fileSet = new ScmFileSet( new File(
releaseDescriptor.getWorkingDirectory() ) );
String tagName = releaseDescriptor.getScmReleaseLabel();
+logInfo( relResult, Tagging release with the label + tagName +
... );
result = provider.tag( repository, fileSet, tagName,
releaseDescriptor.getScmCommentPrefix() +
copy for tag + tagName );
}
{code}
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155634#action_155634
]
Kyle Lebel commented on SCM-406:
This is true. My suggestion is flawed in a scenario where many developers risk
committing to the trunk while building tags. In our situation, there are often
many projects on the go with a manageable amount of developers (2-5) working on
them. While building tags, we communicate to them to not commit to the trunk
until the release is completed.
But obviously this does not cover all scenarios.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155642#action_155642
]
George Gastaldi commented on SCM-406:
-
And how about using SVNKit (http://www.svnkit.com) as the SVN provider ?
Or another java implementation of SVN Client ? Is that possible ?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155652#action_155652
]
Thomas Dreyer commented on SCM-406:
---
Using subversion 1.5.0 is also a good workaround for the moment.
As Peter writes in his blog:
http://osi.fotap.org/2008/07/30/svn-151-breaks-maven-release-plugin/
CollabNet Subversion 1.5.0 download:
http://downloads-guests.open.collab.net/servlets/ProjectDocumentList?folderID=6
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155696#action_155696
]
Alison Winters commented on SCM-406:
I think Torsten is on the right track here. If you svn update the directory
before tagging it will work by using the current directory (.). To protect
against the scenario where someone else might have updated trunk in between i
think we could look at the following fix (sorry for pseudo code, i'm not
familiar enough with the Maven internals to provide a real patch).
{code}
boolean forceUpdate = getForceUpdateArgument();
int revision = getHeadRevision();
if (!forceUpdate hasChanges(revision)) {
println(Head revision has the following changes, do you wish to update?);
printChanges(revision);
if (!yesNo()) {
return;
}
}
update(revision);
doTag(.);
{code}
There is still a tiny race condition where someone checks something into head
in between when you get the latest revision number and when you hit yes in
non-force-update mode, but if that fails then it's no worse than the situation
right now. This will at least fix the case for most of us who have segmented
trees where it is very unlikely we will be tagging something from a branch that
anyone else is simultaneously editing.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155698#action_155698
]
Alison Winters commented on SCM-406:
Just to clarify possible ambiguity in my pseudocode:
getForceUpdateArgument() - command line argument to Maven
getHeadRevision() - svn info http://server/path/to/[EMAIL PROTECTED]
printChanges()/hasChanges() - svn status -u . (filtered to changes $revision)
update() - svn update -r $revision .
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155471#action_155471
]
Kuno Baeriswyl commented on SCM-406:
I'd like to confirm that the problem still exists with svn 1.5.4 and release
plugin 2.0-beta-8 (on Windows). Does anybody know if there is an offical
bugreport from the subversion team I could track?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155565#action_155565
]
Kalle Korhonen commented on SCM-406:
Agree, still a problem in svn 1.5.4, sorry for the noise. Only one of our
project succeeded a release without issues because of a funny side effect of
using the buildnumber plugin - it does svn update as part of the build (if
configured so); which as other have pointed out, you can do manually as well to
continue release:prepare after it fails the first time.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155004#action_155004
]
Kalle Korhonen commented on SCM-406:
Try together with release plugin 2.0-beta-8 - though I'm now seeing some
oddities, need to verify it's not a user error when I release our project the
next time (in a week)
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155017#action_155017
]
Tomislav Stojcevich commented on SCM-406:
-
svn 1.5.4 with release plugin 2.0-beta-8, the problem still exists
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154540#action_154540
]
George Gastaldi commented on SCM-406:
-
Kalle, I upgraded to 1.5.4 and the problem was not solved.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153812#action_153812
]
Matthias Weßendorf commented on SCM-406:
even wores, if your trunk is not named trunk... (b/c it is sometimes that case
to have two trunks (to work on different JSR specs)) but trunk12_x
Anyway, so I run the plugin like :
mvn release:prepare -DprepareRelease=true -Dresume
-Dtag=http://svn.apache.org/repos/asf/myfaces/trinidad/tags/trinidad-1.2.10
now... I get this:
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Server sent unexpected return value (403 Forbidden) in response to
MKACTIVITY request for
'/repos/asf/!svn/act/32a097b1-8097-af46-a3c1-55150b6042bd'
[INFO]
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153836#action_153836
]
Kalle Korhonen commented on SCM-406:
Upgrading to svn 1.5.4 fixes the issue
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153813#action_153813
]
Matthias Weßendorf commented on SCM-406:
for the problem above I had to do this:
http://svn.apache.org/viewvc?view=revrevision=713040
now a mvn release:prepare -DprepareRelease=true -Dresume does the trick:
However, still some clean ups, to be consistent:
http://svn.apache.org/viewvc?view=revrevision=713043
http://svn.apache.org/viewvc?view=revrevision=713044
:-)
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153193#action_153193
]
Kyle Lebel commented on SCM-406:
Hey guys, I downloaded the source code for the multiple dependencies
(maven-release-plugin, maven-release-manager, maven-scm-providers-svn).
If the maven-release-plugin you have is configured to use the latest, it will
use 1.1 version of the maven-scm-providers. Simply changing the following line
162 in SvnTagCommand resolves this issue:
cl.createArgument().setValue( . );
to
cl.createArgument().setValue( repository.getUrl() );
So not sure if someone would want to make an official revision for this. For
now I will deploy this to our local maven repository.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153195#action_153195
]
Kyle Lebel commented on SCM-406:
Actually just after posting my comment I noticed this was already fixed in
1.1.1 - I guess the next step then to make this official is updating
maven-release-plugin / manager? Anyone know the plans for this?
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=150807#action_150807
]
Yann Albou commented on SCM-406:
This issue still happens with SVN 1.5.3
I don't know if it is an issue on SVN or on Maven side, but the issue can be
resolved if we tag from repository instead of tagging from the local version.
There is an open issue on this subject: SCM-262
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149246#action_149246
]
Alison Winters commented on SCM-406:
This does appear to be an SVN bug in the sense that it doesn't let you tag
from a non-head revision, even if all the files in and below the current
directory are in fact at the latest revision for that directory on the
repository. I think perhaps Maven should hide this by explicitly running an
svn up prior to the svn copy - it makes sense anyways because presumably you do
always want to release from the head version of what's in the repository.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147686#action_147686
]
Michael Johns commented on SCM-406:
---
I have a little color I can add to this discussion. We too use Maven, but I'm
99% sure this has nothing to do with it. Here's what I've done:
# Ran a release in Maven; failed with the error everyone else is seeing (svn:
File '...' already exists) 2. In a command prompt on our build box, changed to
the project's working directory that was created by the Maven build. From
there, ran a svn --non-interactive copy -m message . test destination
manually (same command that Maven runs, save for an explicit message rather
than --file). Got the same error.
# Queried the working copy to see if any files were changed. No files were
changed, but about 10 new files were present (relics from the aborted build).
# Deleted the new files and ran the command again. Failed again with same
error.
# Ran an update on my working copy. No changes happened (no new files, deleted
files, or changed files), but something happened because...
# Ran the command again, and it worked.
Some things to note:
* We have a multi-module project.
* We're on Windows Server 2003.
* I installed SVN using various methods (msi, unzip), and they all fail. We
have 1.5.2 with the Apache 2.0 bindings.
* This problem doesn't happen with SVN 1.5.0, but it does happen with 1.5.1.
To me, this most definitely appears to be a SVN bug. I've also posted this to
the subversion users mailing list since it's really more relevant to them. But
I figured I'd cross-post it here to help exonerate Maven as the culprit.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147352#action_147352
]
Grégory Joseph commented on SCM-406:
Has anyone had a chance to test with a 1.5.2 client ? (source released Aug
30th, no binary for osx yet, afaik)
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147355#action_147355
]
Grégory Joseph commented on SCM-406:
Good news, I guess: using the macports.org port of the subversion client 1.5.2,
this now seems to work.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=147386#action_147386
]
James William Dumay commented on SCM-406:
-
I can still confirm this issue with the SVN 1.5.2 release.
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146938#action_146938
]
Vincent Siveton commented on SCM-406:
-
I got this issue. Here are some workarounds from dkulp and olamy:
{noformat}
# mvn release:prepare
= fails
# svn up -r head
# mvn release:prepare -Dresume
{noformat}
using latest svn in your path and call svn cleanup (if you used TortoiseSVN,
kill the TSVNCache too)
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
[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1
[
http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=146561#action_146561
]
James William Dumay commented on SCM-406:
-
Problem has been discussed at length here:
http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html
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
