[
https://issues.jboss.org/browse/JBIDE-13014?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13014:
----------------------------------------
{quote}
Bear in mind too that the simple syntax used by local users to quickly build against the
latest max TP:
mvn clean install -Pmaximum
becomes
mvn clean install -DthirdPartyDepsProfile=maximum
-DjbossToolsDepsProfile=jbosstools-staging-aggregate
{quote}
jbosstools-staging-aggregate is the default value for jbossToolsDepsProfile, so it
becomes
mvn clean install -DthirdPartyDepsProfile=maximum
It's a few characters more, but it's way more explicit and help end-users to
understand that they are choosing a profile, which is not clear with current approach
where people don't understand how profile can be mixed.
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