[jira] [Closed] (MRELEASE-595) release:prepare using old SVN structure when creating tag

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRELEASE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRELEASE-595.
-----------------------------------
    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:prepare using old SVN structure when creating tag
> ---------------------------------------------------------
>
>                 Key: MRELEASE-595
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-595
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)