[ https://jira.jboss.org/jira/browse/JBIDE-4591?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4591: --------------------------------------- Fix Version/s: 3.1.0.M2 Affects Version/s: 3.1.0.M2 (was: 3.1.0.M3) Assignee: Denis Golovin Priority: Blocker (was: Major) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4591?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4591: ----------------------------------- OK, here's the story... We're building feature org.jboss.tools.maven.feature, which includes three plugins: F org.jboss.tools.maven.feature P org.jboss.tools.maven.core P org.jboss.tools.maven.ui P org.jboss.tools.maven.seam So, we can either switch to building the SDK feature (which includes both the maven.feature and the maven.seam.feature, plus sources)... F org.jboss.tools.maven.sdk.feature F org.jboss.tools.maven.feature F org.jboss.tools.maven.source.feature F org.jboss.tools.maven.seam.feature F org.jboss.tools.maven.seam.source.feature ... or I can experiment with building both the maven.feature and the maven.seam.feature, but the second feature doesn't provide anything new - in only includes the maven.seam plugin: F org.jboss.tools.maven.seam.feature P org.jboss.tools.maven.seam -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4591?page=com.atlassian.jira.plu... ] Nick Boldt updated JBIDE-4591: ------------------------------ Attachment: Screenshot.png screenshot showing m2eclipse is installed, as are three jboss maven plugins (ui, core, seam). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4591?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4591: -------------------------------------- The maven core feature is a separate feature because it doesn't depend on JBoss Tools. It contains a facet and ext. points that contribute Maven artifacts to WTP projects. The maven seam feature adds specific functionalities related to JBoss Seam Web Project. It depends on JBoss Tools. This is the only reason why these three plugins are placed in two features. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-4591?page=com.atlassian.jira.plu... ] Nick Boldt commented on JBIDE-4591: ----------------------------------- JBT m2 and trunk have updated assoc'dsites.xml, each one a different URL (0.9.9.200906081351 for m2, updates-dev for trunk). m2e zip used in build for m2 is the same (from 0.9.9.200906081351); trunk now points at the new one m2eclipse-0.9.9.200907071528.zip I trust that should be all for this bug. Need a clean trunk/M3 build before we can close this, but at least it can be moved to M3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira