[ http://jira.codehaus.org/browse/CONTINUUM-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=173318#action_173318
]
Luc Willems commented on CONTINUUM-2172:
----------------------------------------
change the logging of defaultShellCommandHelper and got this out
if ( result != 0 )
{
getLogger().warn("Result: "+result);
getLogger().warn("STDOUT=" + stdOut.toString());
getLogger().warn("STDERR=" + stdErr.toString());
throw ......
}
shellCommandHelper - Result: 1
2009-04-17 19:29:21,473 [pool-3-thread-1] WARN shellCommandHelper - STDOUT=
2009-04-17 19:29:21,474 [pool-3-thread-1] WARN shellCommandHelper - STDERR=Exception in
thread "main" java.lang.NoClassDefFoundError: org/codehaus/classworlds/Launcher
see NoClassDefFountError seems to trigger the error ?
> Release project fails in run-release-prepare-goals
> ---------------------------------------------------
>
> Key: CONTINUUM-2172
> URL: http://jira.codehaus.org/browse/CONTINUUM-2172
> Project: Continuum
> Issue Type: Bug
> Components: Release
> Affects Versions: 1.2.3
> Environment: Ubuntu/Apache 6.0.18/JDK 1.5
> Reporter: Luc Willems
>
> Releasing a "Web application " project (1 pom.xml) fails always during run-release-prepare-goals
> with exception :
> [INFO] Transforming 'xxxxx xxxxx xxxx Applications'...
> [INFO] Not generating release POMs
> [ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed,
exit code: '1'
> at org.apache.continuum.release.phase.AbstractContinuumRunGoalsPhase.execute(AbstractContinuumRunGoalsPhase.java:70)
> at org.apache.continuum.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:47)
> 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:178)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution
failed, exit code: '1'
> at org.apache.continuum.utils.shell.DefaultShellCommandHelper.executeGoals(DefaultShellCommandHelper.java:212)
> at org.apache.continuum.utils.shell.DefaultShellCommandHelper.executeGoals(DefaultShellCommandHelper.java:172)
> at org.apache.continuum.release.phase.AbstractContinuumRunGoalsPhase.execute(AbstractContinuumRunGoalsPhase.java:62)
> ... 11 more
> in continuum log file i find :
> 2009-04-15 13:13:47,880 [pool-3-thread-1] INFO shellCommandHelper - Executing: /bin/sh
-c cd /data/continuum/working/336 && mvn -Dmaven.repo.local=/data/continuum/user/purl
clean integration-test --no-plugin-updates --batch-mode
> if i run this manually (as same user as tomcat is running in) , no 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
|