[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- OK, so we have some decoupling to do for this to work: * devstudio.core.feature INCLUDES devstudio.core.rpm.feature and rpmdeps.feature * devstudio.core.rpm.feature INCLUDES org.jboss.tools.richfaces.feature * org.jboss.tools.richfaces.feature REQUIRES vpe.feature, jsf.feature, jst.feature. * jsf.feature REQUIRES jst.feature and vpe.feature * AND... vpe.feature INCLUDES vpe.preview.feature So therefore if we want to include richfaces.feature but remove vpe.feature and keep vpe.preview.feature, we need to make richfaces.feature not depend on vpe.feature, and vpe.feature can't include vpe.preview feature. This would mean updating feature.xml files, then the update sites' category.xml files and the JBT 4.4.x/Neon marketplace listing (to make sure that previously nested/assumed features are explicitly listed). --- Meanwhile, I see no dependencies on o.j.t.xulrunner (plugin) or on org.jboss.tools.xulrunner.feature (feature). Both org.jboss.tools.vpe.feature and org.jboss.tools.xulrunner.feature include org.jboss.tools.xulrunner.initializer (plugin). So we could remove them from devstudio.rpm, as long as nothing that CONTAINS them drags them back in. First 3 PRs: https://github.com/jbosstools/jbosstools-vpe/pull/345 https://github.com/jbosstools/jbosstools-javaee/pull/416 https://github.com/jbdevstudio/jbdevstudio-product/pull/415/files?w=1 If you agree with this approach, I can show you the changes in update sites' category.xml files too. Or... maybe we want to just remove the richfaces.feature from devstudio entirely? -- This message was sent by Atlassian JIRA (v6.4.11#64026)