[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4257 at 1/30/17 4:32 PM: ----------------------------------------------------------- [~vkadlcik] Currently the RPM only installs two features: * com.jboss.devstudio.core.rpm.feature * com.jboss.devstudio.core.capabilities.feature But these drag in all the dependencies they need to complete the installation, including com.google.guava. I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443 I've moved some more p2 deps out of the rpm (as they're now provided by RPM deps): https://github.com/jbdevstudio/jbdevstudio-product/commit/1d53969a727011d... (order of listed IUs fixed to be in alpha order so the diff looks larger than it might otherwise be) was (Author: nickboldt): [~vkadlcik] Currently the RPM only installs two features: * com.jboss.devstudio.core.rpm.feature * com.jboss.devstudio.core.capabilities.feature But these drag in all the dependencies they need to complete the installation, including com.google.guava. I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443 How can I easily determine which requirements for devstudio have already been met by installed rpms? Or migrate p2 dependencies to rpm dependencies? -- This message was sent by Atlassian JIRA (v7.2.3#72005)