continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Willems (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1572) Release should support Build Environments (formerly called Continuum Profiles)
Date Tue, 23 Sep 2008 06:23:45 GMT


Luc Willems commented on CONTINUUM-1572:

Will this fix also use the CP for the second steps in release phaze ?
will this fix be released in 1.2.1 ?

I think it's important that the release cycle is done in same "environment" that the builds
are defined.
if a user selects a different build environment like MAVEN_OPT,JDK's , maven version , etc
than there is good reason why he is doing that.

so release should run the release cycle in the same environment as the builds. 
this is mandotory to make reproducable releases 

> Release should support Build Environments (formerly called Continuum Profiles)
> ------------------------------------------------------------------------------
>                 Key: CONTINUUM-1572
>                 URL:
>             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.3
> 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:
For more information on JIRA, see:


View raw message