[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3359: ---------------------------------- The reason this happens for JBDS 8.0.0 users (who installed via the installer, and possibly BYOE / marketplace too) is that: JBDS 8.0.0 Branded Product feature *includes* JBDS 8.0.0 Core Features feature which *includes* org.jboss.tools.vpe.browsersim.feature (version="0.0.0" in com.jboss.devstudio.core.feature/feature.xml). For JBDS 8.0.0. that's org.jboss.tools.vpe.browsersim.feature 3.6.0.Final-v20141016-1910-B34. And in JBDS 8.0.2, it's version 3.6.1. So when you attempt to update a single part of JBDS (org.jboss.tools.vpe.browsersim.feature 3.6.0 -> 3.6.1) p2 says you can't because there's a parent feature that *INCLUDES* that child. Solution: update the parent *AND* the child at the same time, via the suggested remediation. As I said before, the workaround here is to either a) update JBDS to 8.0.2, then install stuff from Central, or b) use the remediation option when installing from Central to update JBDS at the same time to 8.0.2 In terms of a solution for JBDS 8.1 that might be slightly better, we can use *require* instead of *include* in the JBDS 8.1 Core Feature, but that will only help for users of the *JBDS BYOE / Marketplace install* method. Users of the installer jar will still have to update everything. Or we can un-reject my proposal from last year to to allow installation of the Core Feature feature in parallel to the Branded Product feature (which we could also extend to all the pieces of JBT inside JBDS, if we wanted). See JBDS-2874. -- This message was sent by Atlassian JIRA (v6.3.11#6341)