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

Daun DeFrance commented on CONTINUUM-2612:
------------------------------------------

Hi Brett.
Forgive my ignorance, I was always doing a prepare in advance of the perform 
and the perform read from the properties.  I tried just going straight to 
perform and it works perfectly.

I apologize for the misunderstanding.

> 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

        

Reply via email to