[ https://issues.jboss.org/browse/JBIDE-24245?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24245: ------------------------------------ After further discussion, we need to treat Fuse like a top-level installation (as we do for testng), so that it can be updated independently of the devstudio product or BYOE feature. Thus, affected files are: * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... (new top-level feature to contain all the Fuse features) * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/categ... (add top-level fuse feature) * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... (add top-level fuse feature) * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... (add top-level fuse feature) * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/installer/... (add top-level fuse feature) And for the RPM: * https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu... (add top-level fuse feature) We should NOT include this new core.fuse.feature in the .product or the core.rpm.feature/feature.xml to avoid Fuse being coupled to a specific devstudio release version. Should Fuse have its own category in the JBT/devstudio update sites? Should we use "FuseDevelopment" and "SOADev", as is done one the JBTIS [1] and JBDSIS [2] sites? [1] http://download.jboss.org/jbosstools/neon/stable/updates/integration-stac... [2] https://devstudio.redhat.com/10.0/stable/updates/integration-stack/10.2.0... -- This message was sent by Atlassian JIRA (v7.2.3#72005)