You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/01/12 21:12:46 UTC
[jira] [Closed] (MRELEASE-522) release plugin tagging don't work
for submodules
[ https://issues.apache.org/jira/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRELEASE-522.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> release plugin tagging don't work for submodules
> ------------------------------------------------
>
> Key: MRELEASE-522
> URL: https://issues.apache.org/jira/browse/MRELEASE-522
> Project: Maven 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: RĂ¼diger 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 was sent by Atlassian JIRA
(v6.3.4#6332)