[
http://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209770#action_209770
]
Ruediger Gubler commented on MRELEASE-522:
------------------------------------------
Keep all modules parallel is a company standard we must follow.
How can we use the comfort of a single shot release with our structure?
> release plugin tagging don't work for submodules
> ------------------------------------------------
>
> Key: MRELEASE-522
> URL: http://jira.codehaus.org/browse/MRELEASE-522
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.0
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_14
> Java home: C:\Programme\Java\jdk1.6.0_14\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Ruediger Gubler
>
> release:prepare doesn't tag submodules which are in different svn path.
> We have the following structure in our svn repositories:
> parentmodule/[trunk|tags|branches]
> module1/[trunk|tags|branches]
> module2/[trunk|tags|branches]
> ...
> moduleN/[trunk|tags|branches]
> I tried to include the modules using <module>../module1</module>
> Which caused to the svn error: the parent directory is not in version control
> After changing the modules to <module>module1</module> and adding the
> submodules via svn:externals into the parent svn directory
> the release:prepare finishes successfully but the submodules are not tagged.
> Yours Rüdiger
--
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
