[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4175: ---------------------------------- For the example of installing Openshift v3 tooling, I get new stuff installed into my ~/.eclipse folder which is OLDER than what's already in rpm install: {code} #➔ find /home/nboldt/.eclipse/ /opt/rh/ -name "*docker.core*" /home/nboldt/.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins/org.eclipse.linuxtools.docker.core_2.1.0.201609141916.jar [from Central / Neon.1] /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.core_2.1.0.201610120918.jar [from RPM / Neon.2] /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.core.source_2.1.0.201610120918.jar {code} So, as a result, Eclipse warns about another singleton version being installed, but not active: {code} org.osgi.framework.BundleException: Could not resolve module: org.eclipse.linuxtools.docker.core [1329] Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.1.0.201610120918"; osgi.identity="org.eclipse.linuxtools.docker.core"; singleton:="true" ss org.eclipse.linuxtools.docker.core id State Bundle 354 ACTIVE org.eclipse.linuxtools.docker.core_2.1.0.201610120918 1329 INSTALLED org.eclipse.linuxtools.docker.core_2.1.0.201609141916 {code} This is not a blocking issue -- just an annoyance caused by the fact that RHSCL has something newer in it than we do in the devstudio TP. We could fix this by moving to newer Docker Tooling bits, but then we'd be moving to Neon.2 a week before GA code freeze. I'll look at some more of these problems next and see if -clean resolves any of the NPEs / eclipse won't start problems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)