[
https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13014:
------------------------------------
Why not just replace
{code}
<activation>
<activeByDefault>false</activeByDefault>
</activation>
{code}
in the two profiles we care about with a new property and a check of that property in each
default-enabled profile?
{code}
<defaults>true</defaults>
and
<property>
<name>defaults</name>
<value>true</value>
</property>
{code}
in the two profiles we want on by default: jbosstools-staging-aggregate, unified.target.
Then you could run like this:
{code}
mvn clean install # run with defaults
or
mvn clean install -Ddefaults=false -Pother,profiles # run with non-defaults
or
mvn clean install -Pother,profiles # run with defaults + others
{code}
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