You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/02/09 19:36:55 UTC

[jira] Updated: (MRELEASE-478) release:prepare creates excessive level in the directory structure when used with SVN client 1.6.3 and up

     [ http://jira.codehaus.org/browse/MRELEASE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MRELEASE-478:
-------------------------------------

    Component/s: prepare

> release:prepare creates excessive level in the directory structure when used with SVN client 1.6.3 and up
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-478
>                 URL: http://jira.codehaus.org/browse/MRELEASE-478
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9
>         Environment: WinXP SP 2, Maven 2.0.9, CollabNet SVN client 1.6.3 or 1.6.5
>            Reporter: Oleksandr Alesinskyy
>
> I have used *release* plugin to perform releases during last 6 months, all have run relatively smoothly but after the recent upgrade of the SVN client to the version  1.6 behavior has changed in the unexpected way - instead of copying of the project directly to the _tag_base_/_tag_ directory in SVN repositiry it copies its now to  the _tag_base_/_tag_/*trunk* directory. Then *prepare* goal fails miserably as it is unable to find project's POM in the target/checkout (as it resides now in the target/checkout/*trunk*).
> If after prepare phase contents of the _tag_base_/_tag_/*trunk*  is moved to _tag_base_/_tag_ manually *perform* succeeds.
> Here are commands used for prepare and release :
> {code}
> call mvn -o -X -e release:prepare  --batch-mode -DdryRun=false -DautoVersionSubmodules=true    -DreleaseVersion=%FBS_VERSION% -DdevelopmentVersion=2.2-SNAPSHOT -DtagBase=%FBS_TAGBASE% -Dtag=%FBS_VERSION%/fbs -DpreparationGoals="clean" 
> call mvn -e release:perform -o --batch-mode -Dgoals=deploy -DtagBase=%FBS_TAGBASE% -Dtag=%FBS_VERSION%/fbs -DuseReleaseProfile=false 
> {code}
> And scm section of the pom.xml
> {code:xml}
>     <scm>
>         <connection>
>             scm:svn:https://devzone-eu.navteq.com/svn_cssd/ffe-dev/components/fbs/trunk
>         </connection>
>         <developerConnection>
>             scm:svn:https://devzone-eu.navteq.com/svn_cssd/ffe-dev/components/fbs/trunk
>         </developerConnection>
>         <url>
>             https://devzone-eu.navteq.com/svn_cssd/ffe-dev/components/fbs/trunk/pom.xml
>         </url>
>     </scm>
> {code}

-- 
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