continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Willems (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-1572) Release should support Build Environments (formerly called Continuum Profiles)
Date Mon, 06 Oct 2008 19:04:09 GMT

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

Luc Willems commented on CONTINUUM-1572:
----------------------------------------

couldn't get it to work :-(

- first try would not release because some prject didn't got a succesfull build (some minor
issues in unit tests)
- add maven.test.skip=1 "quickly" bypass this issues
- got selection menu , selected correct settings and started release
- prepare step failed because of followin error :
....
[INFO] Updating api to 1.1
[INFO] Ignoring artifact version update for expression: ${version}
[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:619)
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:209)
        at org.apache.continuum.utils.shell.DefaultShellCommandHelper.executeGoals(DefaultShellCommandHelper.java:169)
        at org.apache.continuum.release.phase.AbstractContinuumRunGoalsPhase.execute(AbstractContinuumRunGoalsPhase.java:62)

seems like problems using ${version} in parent pom.xml . the finalName was constructed like
pmf-${artifactId}-${version}
- removed this to bypass this problem
- retried release , but pressing Release button doesn't do any thing :-(
- no way to initiate a release, can't find a error in logfiles :-(

luc

> Release should support Build Environments (formerly called Continuum Profiles)
> ------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1572
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1572
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Core - Profiles, Release
>    Affects Versions: 1.1-beta-4, 1.1
>            Reporter: Lóránt Pintér
>            Assignee: Maria Catherine Tan
>             Fix For: 1.2.1
>
>
> Currently there's no way to specify parameters for the release, like JVM version or MAVEN_OPTS.
I had a hard time "configuring" Maven to have enough memory during the release (actually I
had to add MAVEN_OPTS=-Xmx512m as an environment variable -- not a really nice solution).
> It would be nice to have a similar build configuration for the release as we have for
other builds, with profiles and all. Maybe a default schedule called RELEASE would do.

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