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)
Date: Fri, 8 Apr 2011 06:41:22 -0500 (CDT)
From: "Daun DeFrance (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Message-ID: 
 <32294185.51489.1302262882412.JavaMail.haus-jira@codehaus01.managed.contegix.com>
In-Reply-To: 
 <18049311.33280.1300105702289.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Subject: [jira] Closed: (CONTINUUM-2612) Release Perform should allow
 selection of environment for final build
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ http://jira.codehaus.org/browse/CONTINUUM-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daun DeFrance closed CONTINUUM-2612.
------------------------------------

    Resolution: Not A Bug

Misunderstanding of how the perform worked.

> Release Perform should allow selection of environment for final build
> ---------------------------------------------------------------------
>
>                 Key: CONTINUUM-2612
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2612
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Release
>    Affects Versions: 1.3.6
>         Environment: RedHat, Oracle 1.6 JDK, IBM J9 1.6 JDK, IBM J9 1.5 JDK
>            Reporter: Daun DeFrance
>
> We perform three different builds using three jdks configured as environments within continuum.  We also use Maven profiles to specify classifiers for those builds.  For example, our artifacts look like:
> [artifact]-WAS7.ear (built with IBM J9 1.6 JDK)
> [artifact]-JBOSS.ear (built with Oracles 1.6 JDK)
> When we to a prepare release, we are allowed to specify environment.  The prepare relese creates the tag, etc.  However, in our situation, we only want one tag per release number, but we want to generate three released builds off that one tag.  The code is not changed per environment, so one tag is sufficient.
> When we perform a release, we cannot specify an environment (and corresponding Maven profile for the classifier), so we cannot specify a different environment for the release.
> I would like the ability to tag once and generate three different environmental releases builds, each one compiled against a different JDK.
> We are not using distributed builds at this time.

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