[
https://jira.codehaus.org/browse/MRELEASE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=316779#comment-316779
]
Steve van den Buys commented on MRELEASE-595:
---------------------------------------------
I have the same issue on a large multi-module project that is structured the
same way as above (so with trunk/tags/branches and a bunch of other folders
living next to each other in SVN). However: it has always been structured like
this so it is impossible that the plugin is picking up any old SVN structure
(because our current structure and old structure are the same). The plugin
should do as it is told and use the base folder as specified in the scm-section
of the parent-pom and NOT go up a level!
Is there any chance of a quick patch or workaround to get this done? Because as
it is now, the plugin is unusable for us and I do things manually (well: I can
use the update-versions target to at least not have to manually alter the 30+
POMs of our project).
> release:prepare using old SVN structure when creating tag
> ---------------------------------------------------------
>
> Key: MRELEASE-595
> URL: https://jira.codehaus.org/browse/MRELEASE-595
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_18
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Cornel Masson
>
> I made a change in my project's SVN folder structure, and now release:prepare
> is creating the tag using the old structure. Example:
> In my organization, each project has sub-folders for trunk, tags and
> branches. However, my test projectA started out (incorrectly) in SVN
> *without* trunk/tags/branches subfolders:
> {code}
> svnhost/code/projectA:
> /gui
> /model
> -pom.xml
> {code}
> Later, I realised my mistake, created a trunk subfolder under projectA, and
> moved the project contents into trunk. I also added tags and branches folders:
> {code}
> svnhost/code/projectA:
> /trunk
> /gui
> /model
> -pom.xml
> /tags
> /branches
> {code}
> I re-checked out a clean projectA and did release:prepare with tagBase =
> {{svnhost/code/projectA/tags}} and tag name 'MyTag'. It created MyTag, but
> the contents was *all* of trunk/tags/branches(!):
> {code}
> svnhost/code/projectA:
> /trunk
> /gui
> /model
> -pom.xml
> /tags
> /MyTag
> /trunk
> /gui
> /model
> -pom.xml
> /tags
> /branches
> /branches
> {code}
> instead of just using the contents of trunk at that point.
> It looks like it's picking up the *old* SVN structure from the projectA
> folder.
--
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
