[jbosstools-issues] [JBoss JIRA] (JBIDE-13014) Replace activeByDefault

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732916#comment-12732916 ] 

Nick Boldt edited comment on JBIDE-13014 at 11/8/12 1:38 PM:
-------------------------------------------------------------

From: https://github.com/mickaelistria/jbosstools-build/commit/2c0c7933367523368ae63552142d1ebaa7dfd9d2#commitcomment-2123737

{quote}
Currently, a job like the JBT SOA aggregate uses these profiles:

{code}
-P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite
{code}

So with this change we'll have to redo all the jobs to set

{code}
-DjbossToolsDepsProfile=jbosstools-staging-aggregate -DthirdPartyDepsProfile=jenkins.target.maximum (for aggregate builds){code}
 or{code} -DjbossToolsDepsProfile=jbosstools-nightly-staging-composite -DthirdPartyDepsProfile=jenkins.target (component builds),{code}

but no longer have the ability to fall back to an alternate URL should the local NFS mount fails.

Not sure I'm 100% happy with this implementation. Do we only ever want just ONE upstream site w/ JBT bits and ONE upstream site w/ 3rd party bits (TP) ?
{quote}
                
      was (Author: nickboldt):
    From: https://github.com/mickaelistria/jbosstools-build/commit/2c0c7933367523368ae63552142d1ebaa7dfd9d2#commitcomment-2123737

{quote}
Currently, a job like the JBT SOA aggregate uses these profiles:

-P hudson,jbosstools-nightly-staging-composite,jenkins.target.maximum,local.site,local.composite

So with this change we'll have to redo all the jobs to set

-DjbossToolsDepsProfile=jbosstools-staging-aggregate -DthirdPartyDepsProfile=jenkins.target.maximum (for aggregate builds) or -DjbossToolsDepsProfile=jbosstools-nightly-staging-composite -DthirdPartyDepsProfile=jenkins.target (component builds),

but no longer have the ability to fall back to an alternate URL should the local NFS mount fails.

Not sure I'm 100% happy with this implementation. Do we only ever want just ONE upstream site w/ JBT bits and ONE upstream site w/ 3rd party bits (TP) ?
{quote}
                  
> Replace activeByDefault
> -----------------------
>
>                 Key: JBIDE-13014
>                 URL: https://issues.jboss.org/browse/JBIDE-13014
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Build/Releng
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.0.0.CR1
>
>
> Since activeByDefault does automatically get disabled when another profile is enabled (such as osx profile), it's not doing what we want.
> Let's try moving to a property-based approach to select profiles that are exclusive, and the default value of the property will enable the current activeByDefault profile.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira