[
http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121564
]
ajbanck commented on MRELEASE-300:
----------------------------------
Since beginning of December I am having similar problems. I could not find out
what Maven change is causing this but what I found out:
My problem is related to keyword substition. Looks like the pom.xml file is now
kept open by the Java process, not sure where. After commit the file is opened
to write back/substitute the keywords, this is where it fails. Removing keyword
substition and release:prepare worked as before.
Might not be exactly the same issue, but something changed that locks the
pom.xml, causing writes/updates of it on commit to fail.
> Regression: release:prepare fails for svn
> -----------------------------------------
>
> Key: MRELEASE-300
> URL: http://jira.codehaus.org/browse/MRELEASE-300
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Windows, M205, JDK 1.4.2, svn 1.4.2
> Reporter: Joerg Schaible
> Priority: Blocker
>
> After the upgrade to 2.0-beta-7 from 2.0-beta-6 the release:prepare fails at
> the last step:
> ========== %< ===============
> $ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building Elsag Master Project
> [INFO] task-segment: [release:prepare] (aggregator-style)
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] [release:prepare]
> [INFO] Resuming release from phase 'scm-commit-release'
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-84899240.commit --targets
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-13397-targets
> [INFO] Working directory: D:\work\standard\master-pom
> [INFO] Tagging release with the label v_117...
> [INFO] Executing: svn --non-interactive copy --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-1381395764.commit .
> http://websvn/svn/essvn/development/buildsystem/maven-2/master-pom/tags/v_117
> [INFO] Working directory: D:\work\standard\master-pom
> [INFO] Transforming 'Elsag Master Project'...
> [INFO] Not removing release POMs
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --non-interactive commit --file
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-1672780400.commit --targets
> c:\DOKUME~1\jos\LOKALE~1\Temp\maven-scm-13398-targets
> [INFO] Working directory: D:\work\standard\master-pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: Commit succeeded, but other errors follow:
> svn: Error bumping revisions post-commit (details follow):
> svn: In directory 'D:\work\standard\master-pom'
> svn: Error processing command 'committed' in 'D:\work\standard\master-pom'
> svn: Error replacing text-base of 'pom.xml'
> svn: Can't move 'D:\work\standard\master-pom\.svn\tmp\pom.xml.tmp' to
> 'D:\work\standard\master-pom\pom.xml': Zugriff verweigert
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 21 seconds
> [INFO] Finished at: Tue Nov 27 11:59:30 CET 2007
> [INFO] Final Memory: 5M/10M
> [INFO]
> ------------------------------------------------------------------------
> ========== %< ===============
> After switching back to 2.0.-beta-6, the step works flawlessly.
--
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
