[jbosstools-issues] [JBoss JIRA] (JBDS-4175) RPM version: NPE after install from Red Hat Central

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13322944#comment-13322944 ] 

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.

> RPM version: NPE after install from Red Hat Central
> ---------------------------------------------------
>
>                 Key: JBDS-4175
>                 URL: https://issues.jboss.org/browse/JBDS-4175
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: central-update, rpm
>         Environment: RHEL 7.2 with RHSCL repositories available:
>  * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1.1/compose/Server/x86_64/os/)
>  * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23z/v02/)
>            Reporter: Václav Kadlčík
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 10.2.0.GA
>
>         Attachments: JBDS-4175_logs_first_half.tar.gz, sw_to_install.txt, workspace.log
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)