You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ruediger Gubler (JIRA)" <ji...@codehaus.org> on 2010/02/11 13:02:55 UTC
[jira] Created: (MRELEASE-522) release plugin tagging don't work
for submodules
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
[jira] (MRELEASE-522) release plugin tagging don't work for
submodules
Posted by "Luke Rathbone (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314401#comment-314401 ]
Luke Rathbone commented on MRELEASE-522:
----------------------------------------
We have several projects in this format. In this real world case, sometimes the modules are released independently, sometimes they are all released at the same time. Each module _must_ have it's own trunk to accommodate this. The key here is that we are being *flexible*. It would be nice to move this flexibility into the plugin.
I've tried experimenting with {{tagBase}} and {{connectionUrl}}, but didn't get anywhere. Is there anything we can add to the plugin configuration as a workaround?
> release plugin tagging don't work for submodules
> ------------------------------------------------
>
> Key: MRELEASE-522
> URL: https://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, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-522) release plugin tagging don't work
for submodules
Posted by "Ruediger Gubler (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-522) release plugin tagging don't work
for submodules
Posted by "Nicola Musatti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232222#action_232222 ]
Nicola Musatti commented on MRELEASE-522:
-----------------------------------------
Using separate trunks makes it easier for different developers to use different aggregator projects, that only contain the modules they actually work on. They also help avoid making customer specific customizations an all or nothing affair.
Automatic recognition of externals linked modules or, alternatively, a specific, explicit option would be very useful.
> 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
[jira] Commented: (MRELEASE-522) release plugin tagging don't work
for submodules
Posted by "werner mueller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242253#action_242253 ]
werner mueller commented on MRELEASE-522:
-----------------------------------------
this structure is a bit unusual.
have you tried to reproduce the plugin config and the scm in the modules?
of if you have a common parent use some properties and overwrite them in the submodules?
this would mean you have to add the release-plugin config or the properties into every module-pom but that should work?
> 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
[jira] Commented: (MRELEASE-522) release plugin tagging don't work
for submodules
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209767#action_209767 ]
Brett Porter commented on MRELEASE-522:
---------------------------------------
This is presently by design. It is designed to work on a multi-module project that shares a common source root.
If you require separate trunks that is a strong indicator that your projects are on separate release schedules - in which case they should be released independently. IF they are on the same release schedule as you are attempting, you would benefit from placing them under a single trunk.
> 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