continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Lustig (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-1513) Release does not work when maven 2 executable is not on PATH
Date Thu, 15 Jan 2009 09:59:20 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160991#action_160991
] 

Marc Lustig commented on CONTINUUM-1513:
----------------------------------------

Is it save to install tomorrow's nightly build from vmbuild.apache.org, or is the trunk not
very stable currently?

Btw, vmbuild.apache.org doesn't show any project groups to me anymore.
Could somebody please assign the rights.

> Release does not work when maven 2 executable is not on PATH
> ------------------------------------------------------------
>
>                 Key: CONTINUUM-1513
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1513
>             Project: Continuum
>          Issue Type: Bug
>          Components: Environmental
>    Affects Versions: 1.1-beta-3
>         Environment: Maven 2 executable NOT ON PATH, just on profile
>            Reporter: George Gastaldi
>            Assignee: Maria Catherine Tan
>             Fix For: 1.3.1
>
>         Attachments: wrapper.20071005.log
>
>
> When trying to release a project, when maven 2 is not on the path, the following error
occurs:
> {code}
> [INFO] Updating local copy against the scm...
> [INFO] Verifying that there are no local modifications...
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO] Transforming 'aarh-bridge_visao'...
> [INFO] Not generating release POMs
> [ERROR] org.apache.maven.shared.release.ReleaseExecutionException: Maven execution failed,
exit code: '127'
> at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:66)
> at org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42)
> 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: org.apache.maven.shared.release.exec.MavenExecutorException: Maven execution
failed, exit code: '127'
> at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:103)
> at org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(ForkedMavenExecutor.java:121)
> at org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:59)
> ... 11 more
> {code}
> It appears that the continuum release feature do not respect the build profile for maven
2.
> Attached is the log file.

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

        

Mime
View raw message