[
https://issues.apache.org/jira/browse/SCM-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964440#comment-17964440
]
Olivier Lamy commented on SCM-274:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#492|https://github.com/apache/maven-scm/issues/492].
> Support tagging with non-standard svn repository layout
> --------------------------------------------------------
>
> Key: SCM-274
> URL: https://issues.apache.org/jira/browse/SCM-274
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-svn
> Reporter: Alexander Schwartz
> Priority: Major
>
> 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
(v8.20.10#820010)
