maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve van den Buys (JIRA)" <>
Subject [jira] (MRELEASE-595) release:prepare using old SVN structure when creating tag
Date Fri, 04 Jan 2013 23:50:13 GMT


Steve van den Buys commented on MRELEASE-595:

Ah, I just noticed the following in the docs (regarding the URL to use for developerConnection):

"The developerConnection contains the URL of the Source Control Management system pointing
to the folder containing this pom.xml"

That is not the case in my parent POM: this points to trunk but, if I interpret the above
sentence correctly, this should be:


It is too late for me to try this now (past midnight over here) but I'm guessing the above
is the solution to my problem!
> release:prepare using old SVN structure when creating tag
> ---------------------------------------------------------
>                 Key: MRELEASE-595
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message