Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <25073522.1222151025933.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Tue, 23 Sep 2008 01:23:45 -0500 (CDT)
From: "Luc Willems (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Commented: (CONTINUUM-1572) Release should support Build
 Environments (formerly called Continuum Profiles)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


    [ http://jira.codehaus.org/browse/CONTINUUM-1572?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D148765=
#action_148765 ]=20

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 , mave=
n version , etc ...,=20
than there is good reason why he is doing that.

so release should run the release cycle in the same environment as the buil=
ds.=20
this is mandotory to make reproducable releases=20


> Release should support Build Environments (formerly called Continuum Prof=
iles)
> -------------------------------------------------------------------------=
-----
>
>                 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=F3r=E1nt Pint=E9r
>            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=3D-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.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: htt=
p://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira