You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2007/01/18 10:32:10 UTC

[jira] Commented: (SCM-274) Support tagging with non-standard svn repository layout

    [ http://jira.codehaus.org/browse/SCM-274?page=comments#action_85339 ] 
            
Emmanuel Venisse commented on SCM-274:
--------------------------------------

ok, but the patch must be generic so other providers will can implement it too.

> Support tagging with non-standard svn repository layout 
> --------------------------------------------------------
>
>                 Key: SCM-274
>                 URL: http://jira.codehaus.org/browse/SCM-274
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-svn
>            Reporter: Alexander Schwartz
>
> There is a non-standard, but common svn repository layout & tagging/branching convention: The repository has three top-level folders
>    /trunk
>    /branches
>    /tags
> If a module is tagged it is copied into to the tag base followed by the tag name and by the full module path.
> Example: Assume we would like to tag version 1.1.0 of the module org/sample/module1. We use the tag "org_sample_module1_20070118_1_1_0".
> After tagging the repo looks as follows.
>    /trunk
>         /org/sample/module1/pom.xml                        
>   /branches
>   /tags
>       /org_sample_module1_20070118_1_1_0/org/sample/module1/pom.xml
> (There are several good arguments for such an repository layout. 
> My main argument is that this layout communicates what is in a tag directory.)
> The following modifications are necessary to resolve this issue:
>   -- A new property "modulePath" is introduced. It contains the relative module path (here: "org/sample/module1").
>   -- Before the svn tag command is executed a series of scm mkdir commands is executed to create the parent directories.
> If this issue is accepted I am going to provide a patch.

-- 
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