[
https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13014:
----------------------------------------
After a quick call, Max suggestion looks ok to me. I'm working on some improvements to
its branch, as described in
http://ether-man.rhcloud.com/p/parentnext
We'll hopefully come with all the flexibility we want, without changing how end-users
have to use flags, and with dozens of line saved in the pom.xml.
The general idea is to replace plugin configuration in profile by simple properties
settings, and use these properties later.
The default value of these properties constitutes the "default". Profiles only
override the default.
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