You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Philippe Laflamme (JIRA)" <ji...@codehaus.org> on 2009/03/11 16:33:12 UTC
[jira] Commented: (MRELEASE-343) Support for non-standard SVN
structure
[ http://jira.codehaus.org/browse/MRELEASE-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168901#action_168901 ]
Philippe Laflamme commented on MRELEASE-343:
--------------------------------------------
Tag suffix would be help under a standard SVN structure also:
project
/trunk
/tags
/branches
We put release tags and branches under "releases":
project
/trunk
/tags/releases/1.1.3
/branches/releases/1.1.x
Having a suffix would allow use to not specify the tagBase (we're using a standard layout) but only the suffix: releases.
Supporting both tags and branches is important.
> Support for non-standard SVN structure
> --------------------------------------
>
> Key: MRELEASE-343
> URL: http://jira.codehaus.org/browse/MRELEASE-343
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare, scm
> Reporter: Duan Krian
>
> I have non-standard SVN structure. It looks like this:
> big-project-name / trunk / java
> big-project-name / trunk / c++
> It would be nice to configure the release plug-in to release into:
> big-project-name / tags / version-1.0 / java
> In current version I am not able to set "tagBase". In every case I end up with version at the end of the path like:
> big-project-name / tags / java / version-1.0
> It would be enough to create new configuration variable as "tagSuffix" and set:
> tagBase: big-project-name / tags
> tagSuffix: java
--
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