You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@codehaus.org> on 2007/11/27 12:15:57 UTC
[jira] Created: (MRELEASE-300) Regression: release:prepare fails
for svn
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
[jira] Commented: (MRELEASE-300) Regression: release:prepare fails
for svn
Posted by "Nathan Beyer (Cerner) (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120091 ]
Nathan Beyer (Cerner) commented on MRELEASE-300:
------------------------------------------------
I just ran into this exact same error on Windows Vista, Sun JDK 5u14, SVN 1.4.5. I've been releasing code with 2.0-beta-7 since it was released, so I didn't think it was that. The only thing I could narrow it down to is the cobertura plugin in the POM build and reporting sections. I just started using it and this was the first project I was going to release with it. I have no idea what the root problem is, but removing cobertura from the POM did fix the problem and I was able to release.
For whatever that's worth ...
> 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
[jira] Commented: (MRELEASE-300) Regression: release:prepare fails
for svn
Posted by "ajbanck (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-300) Regression: release:prepare fails
for svn
Posted by "Mauritz Lovgren (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121773 ]
Mauritz Lovgren commented on MRELEASE-300:
------------------------------------------
The keyword resolve problem was my problem, too.
I removed svn keywords from all my pom.xml files to get around this.
> 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
[jira] Commented: (MRELEASE-300) Regression: release:prepare fails
for svn
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120154 ]
Joerg Schaible commented on MRELEASE-300:
-----------------------------------------
Interesting. Yes, we use the Cobertura also, but it works with 2.0-beta-6 without any problems for months.
> 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
[jira] Closed: (MRELEASE-300) Regression: release:prepare fails for
svn
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-300.
---------------------------------
Resolution: Won't Fix
> 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