[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Václav Kadlčík commented on JBDS-4257: -------------------------------------- Hmm, I'm afraid that blacklisting specific capabilities on the Devstudio side isn't a practical approach. We would need to list all the Requires of rh-eclipse46 and all its dependencies, recursively. Then blacklist them in Devstudio. Repeat every time anything changes in rh-eclipse46 (or in any of its dependencies). I'd prefer a conservative way: Let rh-eclipse46-devstudio provide just the "end" capabilities (rh-eclipse46-devstudio and rh-eclipse46-devstudio(x86-46)). Maybe the ones specific to Devstudio - various rh-eclipse46-osgi(com.jboss.devstudio.*) can be declared, too, although we don't have an actual usage for them at this moment. But let's cut the rest out and put them back only when we really want to offer them as a dependency. Just an illustration: * rh-eclipse46-osgi(com.google.guava) = 18.0.0 is offered by: * rh-eclipse46-guava-18.0-6.2.el7.noarch * rh-eclipse46-devstudio-10.3-0.20170125.0958.el7.x86_64 I don't think we really need or want rh-eclipse46-devstudio to "publicly" satisfy the capability... -- This message was sent by Atlassian JIRA (v7.2.3#72005)