[
https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13014:
----------------------------------------
but why is the patch I did not sufficient ?
Your commit says:
{quote}
Unfortunately not found any good way of having it automatic disable if any other profile
enabled
thus for now you'll have to do -Dnostaging-aggregate to disable it.
{quote}
I think what we've been missing so far is the implementation of exclusive profiles, so
we've always used workaround to provide a comparable approach. The implementation
I'm suggesting here use properties to select profiles, so the activeByDefault simply
becomes the selector for a profile.
It's closer from the process of *choosing* a profile, and it does not restrict usage
of other profiles (such as macosx profiles)
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