You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2014/05/11 19:23:10 UTC
[jira] (SCM-274) Support tagging with non-standard svn repository
layout
[ https://jira.codehaus.org/browse/SCM-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated SCM-274:
------------------------------
Description:
There is a non-standard, but common svn repository layout & tagging/branching convention: The repository has three top-level folders
{noformat} /trunk
/branches
/tags{noformat}
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.
{noformat} /trunk
/org/sample/module1/pom.xml
/branches
/tags
/org_sample_module1_20070118_1_1_0/org/sample/module1/pom.xml{noformat}
(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.
was:
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.
> Support tagging with non-standard svn repository layout
> --------------------------------------------------------
>
> Key: SCM-274
> URL: https://jira.codehaus.org/browse/SCM-274
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Reporter: Alexander Schwartz
> Fix For: future
>
>
> There is a non-standard, but common svn repository layout & tagging/branching convention: The repository has three top-level folders
> {noformat} /trunk
> /branches
> /tags{noformat}
> 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.
> {noformat} /trunk
> /org/sample/module1/pom.xml
> /branches
> /tags
> /org_sample_module1_20070118_1_1_0/org/sample/module1/pom.xml{noformat}
> (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 was sent by Atlassian JIRA
(v6.1.6#6162)