[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16649: -------------------------------- Description: -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.- -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.- Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly. was: -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.- -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.- Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly. -- 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