You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Jacobsen (JIRA)" <ji...@codehaus.org> on 2007/08/10 11:33:13 UTC

[jira] Created: (CONTINUUM-1382) Continuum release does not work well with Maven2 and Perforce SCM provider (files are locked so release prepare fails)

Continuum release does not work well with Maven2 and Perforce SCM provider (files are locked so release prepare fails)
----------------------------------------------------------------------------------------------------------------------

                 Key: CONTINUUM-1382
                 URL: http://jira.codehaus.org/browse/CONTINUUM-1382
             Project: Continuum
          Issue Type: Bug
          Components: Integration - Maven 2, SCM
    Affects Versions: 1.1-beta-1
         Environment: Windows XP
            Reporter: Brian Jacobsen


Although stated that this is fixed in 1.1alpha2 (Continuum-1270) I still have this issue with the 1.1-beta-1 release.

[INFO] Updating local copy against the scm...
[INFO] Verifying that there are no local modifications...
[INFO] Checking dependencies and plugins for snapshots ...
[ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Error writing POM: C:\TEMP\working-directory-beta1\1\pom.xml (Access is denied)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:678)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:623)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:193)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99)
	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194)
	at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107)
	at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43)
	at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
	at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.FileNotFoundException: C:\TEMP\working-directory-beta1\1\pom.xml (Access is denied)
	at java.io.FileOutputStream.open(Native Method)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
	at java.io.FileWriter.<init>(FileWriter.java:73)
	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:659)
	... 14 more


Manually patching the scm-perforce-provider implementation as suggested in Continuum-1270 and bundling it with Continuum seems to fix the problem.


-- 
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: (CONTINUUM-1382) Continuum release does not work well with Maven2 and Perforce SCM provider (files are locked so release prepare fails)

Posted by "Brian Jacobsen (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/CONTINUUM-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104511 ] 

Brian Jacobsen commented on CONTINUUM-1382:
-------------------------------------------

It should read CONTINUUM-1274 and not CONTINUUM-1270. Sorry for the incovinience.

> Continuum release does not work well with Maven2 and Perforce SCM provider (files are locked so release prepare fails)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1382
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1382
>             Project: Continuum
>          Issue Type: Bug
>          Components: Integration - Maven 2, SCM
>    Affects Versions: 1.1-beta-1
>         Environment: Windows XP
>            Reporter: Brian Jacobsen
>
> Although stated that this is fixed in 1.1alpha2 (Continuum-1270) I still have this issue with the 1.1-beta-1 release.
> [INFO] Updating local copy against the scm...
> [INFO] Verifying that there are no local modifications...
> [INFO] Checking dependencies and plugins for snapshots ...
> [ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Error writing POM: C:\TEMP\working-directory-beta1\1\pom.xml (Access is denied)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:678)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:623)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:193)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:116)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.execute(AbstractRewritePomsPhase.java:99)
> 	at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:194)
> 	at org.apache.maven.shared.release.DefaultReleaseManager.prepareWithResult(DefaultReleaseManager.java:107)
> 	at org.apache.maven.continuum.release.executors.PrepareReleaseTaskExecutor.execute(PrepareReleaseTaskExecutor.java:43)
> 	at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
> 	at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
> 	at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
> 	at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> 	at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> 	at java.lang.Thread.run(Thread.java:595)
> Caused by: java.io.FileNotFoundException: C:\TEMP\working-directory-beta1\1\pom.xml (Access is denied)
> 	at java.io.FileOutputStream.open(Native Method)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
> 	at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
> 	at java.io.FileWriter.<init>(FileWriter.java:73)
> 	at org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.writePom(AbstractRewritePomsPhase.java:659)
> 	... 14 more
> Manually patching the scm-perforce-provider implementation as suggested in Continuum-1270 and bundling it with Continuum seems to fix the problem.

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