Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.2
-
Component/s: maven-scm-provider-svn
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
In theory, you shouldn't tag or branch from a local and potentially different version of the code. From what I can tell, the scm:tag imports your existing code into a new tag. With subversion, tagging is very lightweight if you do a 'svn copy trunk_url tag_url'. The way it currently works make sense for other repositories such as CVS but not for subversion.
Issue Links
- is related to
-
SCM-406
scm tag does not work with Subversion 1.5.1
-
- relates to
-
MRELEASE-427
Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)
-
In my setup SVN repository is multiproject setup and tags/ directory can only be created in. It can't be modified.
I'm unable to use "svn release:prepare" due to it trying to do "svn copy . tag_url". I've made a patch that does "svn copy trunk_rul tag_url" and that makes it work fine. I think this is the right approach in general and is also more efficient from SVN perspective. Is there any chance this issue will be addressed in next release?
Index: src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java
===================================================================
— src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java (revision 586574)
+++ src/main/java/org/apache/maven/scm/provider/svn/svnexe/command/tag/SvnTagCommand.java (working copy)
@@ -157,7 +157,8 @@
cl.createArgument().setValue( messageFile.getAbsolutePath() );
+ String projectRoot = SvnTagBranchUtils.getProjectRoot(repository.getUrl());
+ cl.createArgument().setValue( projectRoot + "/trunk" );
// Note: this currently assumes you have the tag base checked out too
String tagUrl = SvnTagBranchUtils.resolveTagUrl( repository, new ScmTag
( tag ) );