[JBoss JIRA] (JBDS-4188) help docs cannot be opened
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4188:
--------------------------------
Summary: help docs cannot be opened
Key: JBDS-4188
URL: https://issues.jboss.org/browse/JBDS-4188
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, rpm, webservices
Affects Versions: 10.2.0.AM2
Reporter: Nick Boldt
Assignee: Jeff MAURY
Priority: Minor
Fix For: 10.x
As of the latest rpm build [1] I'm only getting this one error now:
{code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
!MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
!STACK 0
org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4162) unresolved bundles - slf4j
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4162?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-4162.
------------------------------
Resolution: Done
I've put slf4j 1.7.2 back into the install so that it need not be installed whenever an unrelated thing gets installed/updated into the rpm install via an update site.
https://github.com/jbdevstudio/jbdevstudio-product/commit/a30844e56cd6812...
Resolving.
> unresolved bundles - slf4j
> ---------------------------
>
> Key: JBDS-4162
> URL: https://issues.jboss.org/browse/JBDS-4162
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rhscl, rpm, target-platform
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: who-uses_ch.qos.logback.slf4j_1.0.7.png, who-uses_slf4j.impl.log4j12_1.7.2.png
>
>
> Vaclav said:
> {quote}
> Just an update on unresolved bundles. I looked at rh-eclipse46-devstudio-10.2-0.20161103.0650.el7.x86_64.rpm and the only ones are:
> ch.qos.logback.slf4j
> org.slf4j.impl.log4j12{quote}
> Both of those bundles declare
> {code}Fragment-Host: org.slf4j.api;bundle-version="[1.7.2,1.7.3)"{code}
> And since we're now using slf4j.api_1.7.4.jar, which has in its MANIFEST.MF:
> {code}
> Export-Package: org.slf4j;version=1.7.4, org.slf4j.spi;version=1.7.4,
> org.slf4j.helpers;version=1.7.4
> Import-Package: org.slf4j.impl;version=1.6.0;resolution:=optional
> Bundle-SymbolicName: slf4j.api
> {code}
> I suspect we need to find newer versions of those that can use slf4j 1.7.4 instead of 1.7.2.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4184 at 11/17/16 4:41 PM:
------------------------------------------------------------
OOTB, devstudio doesn't know about its installed features, only its installed plugins.
!installation-doesn-show-plugins.png|thumbnail!
!installation-doesn-show-features2.png|thumbnail!
!installation-doesn-show-features.png|thumbnail!
But, after installing one or more things from Central (or anywhere else) we get a "migration" wizard [1] triggered.
[1] http://prapicault.blogspot.ca/2013/03/shared-installs-just-got-better.html
Once that process is done, Help > About shows what we expect (more installed content and the correct buttons on the Help > About dialog)...
!installation-does-show-installl-after-migration.png|thumbnail!
And a check for updates shows available updates...
!installation-does-show-avail-updates-after-migration.png|thumbnail!
So... updates ARE available, once migration is triggered and all the correct metadata needed for p2 to do its job correctly is generated.
was (Author: nickboldt):
OOTB, devstudio doesn't know about its installed features, only its installed plugins.
!installation-doesn-show-plugins.png|thumbnail!
!installation-doesn-show-features2.png|thumbnail!
!installation-doesn-show-features.png|thumbnail!
But, after installing one or more things from Central (or anywhere else) we get a "migration" dialog triggered. Once that process is done, Help > About shows what we expect (more installed content and the correct buttons on the Help > About dialog)...
!installation-does-show-installl-after-migration.png|thumbnail!
And a check for updates shows available updates...
!installation-does-show-avail-updates-after-migration.png|thumbnail!
So... updates ARE available, once migration is triggered and all the correct metadata needed for p2 to do its job correctly is generated.
> Can't update/install plugins
> ----------------------------
>
> Key: JBDS-4184
> URL: https://issues.jboss.org/browse/JBDS-4184
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL 7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: installation-does-show-avail-updates-after-migration.png, installation-does-show-installl-after-migration.png, installation-doesn-show-features.png, installation-doesn-show-features2.png, installation-doesn-show-plugins.png, rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
>
>
> I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
> [1] https://devstudio.redhat.com/10.0/snapshots/updates/
> Eclipse was not able to detect any updates (I got "No updates were found" message).
> Then I tried to install plugins using "Install new software".
> Install new software->select Bring Your Own Eclipse->next->restart
> Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
> [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
> [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
> I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4184:
----------------------------------
OOTB, devstudio doesn't know about its installed features, only its installed plugins.
!installation-doesn-show-plugins.png|thumbnail!
!installation-doesn-show-features2.png|thumbnail!
!installation-doesn-show-features.png|thumbnail!
But, after installing one or more things from Central (or anywhere else) we get a "migration" dialog triggered. Once that process is done, Help > About shows what we expect (more installed content and the correct buttons on the Help > About dialog)...
!installation-does-show-installl-after-migration.png|thumbnail!
And a check for updates shows available updates...
!installation-does-show-avail-updates-after-migration.png|thumbnail!
So... updates ARE available, once migration is triggered and all the correct metadata needed for p2 to do its job correctly is generated.
> Can't update/install plugins
> ----------------------------
>
> Key: JBDS-4184
> URL: https://issues.jboss.org/browse/JBDS-4184
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL 7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: installation-does-show-avail-updates-after-migration.png, installation-does-show-installl-after-migration.png, installation-doesn-show-features.png, installation-doesn-show-features2.png, installation-doesn-show-plugins.png, rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
>
>
> I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
> [1] https://devstudio.redhat.com/10.0/snapshots/updates/
> Eclipse was not able to detect any updates (I got "No updates were found" message).
> Then I tried to install plugins using "Install new software".
> Install new software->select Bring Your Own Eclipse->next->restart
> Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
> [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
> [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
> I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4184:
-----------------------------
Attachment: installation-does-show-avail-updates-after-migration.png
installation-does-show-installl-after-migration.png
> Can't update/install plugins
> ----------------------------
>
> Key: JBDS-4184
> URL: https://issues.jboss.org/browse/JBDS-4184
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL 7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: installation-does-show-avail-updates-after-migration.png, installation-does-show-installl-after-migration.png, installation-doesn-show-features.png, installation-doesn-show-features2.png, installation-doesn-show-plugins.png, rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
>
>
> I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
> [1] https://devstudio.redhat.com/10.0/snapshots/updates/
> Eclipse was not able to detect any updates (I got "No updates were found" message).
> Then I tried to install plugins using "Install new software".
> Install new software->select Bring Your Own Eclipse->next->restart
> Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
> [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
> [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
> I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4184) Can't update/install plugins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4184?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4184:
-----------------------------
Attachment: installation-doesn-show-plugins.png
installation-doesn-show-features2.png
installation-doesn-show-features.png
> Can't update/install plugins
> ----------------------------
>
> Key: JBDS-4184
> URL: https://issues.jboss.org/browse/JBDS-4184
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.GA
> Environment: RHEL 7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: installation-doesn-show-features.png, installation-doesn-show-features2.png, installation-doesn-show-plugins.png, rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt, rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt
>
>
> I tried "Check for Updates" in DevStudio 20161116.1305 and 20161113.1010. I used this update site:
> [1] https://devstudio.redhat.com/10.0/snapshots/updates/
> Eclipse was not able to detect any updates (I got "No updates were found" message).
> Then I tried to install plugins using "Install new software".
> Install new software->select Bring Your Own Eclipse->next->restart
> Eclipse didn't detect any problems or conflicts during installation but after restart I got a lot of errors and eclipse didn't start.
> [^rh-eclipse46-devstudio10.2.log.20161116.1305_update_2.txt]
> [^rh-eclipse46-devstudio10.2.log.20161113.1010_update.txt]
> I also noticed there isn't update site [1] by default after installation. I had to add it.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4180 at 11/17/16 3:33 PM:
------------------------------------------------------------
>> ftp://fr2.rpmfind.net/linux/centos/7.2.1511/updates/x86_64/Packages/java-...
>> http://download.devel.redhat.com/released/OpenJDK/8u102/java-1.8.0-openjd...
was (Author: nickboldt):
>> ftp://fr2.rpmfind.net/linux/centos/7.2.1511/updates/x86_64/Packages/java-...
> ClassNotFoundException thrown on devstudio start up
> ---------------------------------------------------
>
> Key: JBDS-4180
> URL: https://issues.jboss.org/browse/JBDS-4180
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: foundation, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output
> {code}
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> Noop constructor
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
> problem is with openjdk version. With the lates 1.8.0_111 it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4180:
----------------------------------
>> ftp://fr2.rpmfind.net/linux/centos/7.2.1511/updates/x86_64/Packages/java-...
> ClassNotFoundException thrown on devstudio start up
> ---------------------------------------------------
>
> Key: JBDS-4180
> URL: https://issues.jboss.org/browse/JBDS-4180
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: foundation, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When starting latest DevStudio 10.2.0.GA (build ID GA-v20161116-0039-B6472) I get following error in console output
> {code}
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> Noop constructor
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.validateClassPathAndLibraryPath(Tools.java:365)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:115)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> java.lang.ClassNotFoundException: sun.jvmstat.monitor.MonitoredHost
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.ContextFinder.loadClass(ContextFinder.java:132)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeGetMonitoredHost(Tools.java:513)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.invokeActiveVms(Tools.java:525)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
> problem is with openjdk version. With the lates 1.8.0_111 it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4175:
----------------------------------
With commits in https://github.com/jbdevstudio/jbdevstudio-product/commits/master in the last 2 days, these constraint violations *SHOULD* now be resolved.
See latest comment w/ steps to repro/verify here:
https://issues.jboss.org/browse/JBDS-4183?focusedCommentId=13324407&page=...
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> 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....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.GA
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> 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
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4183) Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4183?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4183:
----------------------------------
So... with some tweaks to the specfile for the devstudio RPM, I now have a number of working symlinks, which prevent constraint violations for slf4j and httpcomponents.httpclient.
Steps to verify:
{quote}
1. install from latest rpm
2. Help > Install New > https://devstudio.redhat.com/10.0/snapshots/updates/ *{color:red}NOT from STABLE or Central {color}*
3. uncheck "group items by category"
4. select cordovasim feature (v20161115 or newer)
5. restart when prompted
6. ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins
Should not see anything from java.servlet(.api), org.apache.httpcomponents.httpclient(.cache)
But will likely see org.slf4j.api 1.7.2, which is probably OK as it's needed by other *slf4j* jars in the devstudio rpm install
7. install the rpm feature to update everything in devstudio to latest snapshot version from https://devstudio.redhat.com/10.0/snapshots/updates/
8. install all categorized features from https://devstudio.redhat.com/10.0/snapshots/updates/
Result:
{code}#➔ ls .eclipse/org.eclipse.platform_*_linux_gtk_x86_64/{plugins,features} | egrep -v "org.jboss.tools|org.eclipse.thym|org.jboss.ide|hibernate|com.jboss.devstudio"
.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/features:
org.eclipse.linuxtools.vagrant.feature_2.1.0.201609141916
.eclipse/org.eclipse.platform_283378046_linux_gtk_x86_64/plugins:
org.apache.commons.lang_2.6.0.v201404270220.jar
org.apache.xml.resolver_1.2.0.v201005080400.jar
org.apache.xml.serializer_2.7.1.v201005080400.jar
org.eclipse.jetty.rewrite_9.3.9.v20160517.jar
org.eclipse.linuxtools.vagrant.core_2.0.0.201609141916.jar
org.eclipse.linuxtools.vagrant.docs_2.0.0.201609141916.jar
org.eclipse.linuxtools.vagrant.ui_2.0.0.201609141916.jar
org.slf4j.api_1.7.2.v20121108-1250.jar{code}
9. install *everything* from central (using the snapshots site in the background - you can verify this by looking for m2e feature - org.eclipse.m2e.feature.feature.group - 1.7.1.20161104-1805, not something older).
10. On restart, Eclipse {color:red}*crashed*{color}... but when I restarted in a fresh workspace, it opened fine, despite some {color:orange}*NPE from ZeroTurnaround*{color} and the *{color:green}expected{color}* "Another singleton bundle selected" warnings caused by Eclipse's inability to remove old singletons from the /opt/rh folder which are also now installed in ~/eclipse/.{quote}
> Installing from an update site into rpm install causes duplicate IUs to be installed - use constraint violations ensue
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4183
> URL: https://issues.jboss.org/browse/JBDS-4183
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: install-thym.png, rh-eclipse46-devstudio10.2.log.20161116-1226_strict.txt
>
>
> Steps to repro:
> 1. install from latest rpm, eg., 10.2.0.20161116.1342.el7
> 2. open Central > Software/Update, scroll down until you find the *Maven Integration for Eclipse JDT APT (m2e-apt)* connector
> 3. Install it. When prompted to restart, shut down Eclipse and check in your ~/.eclipse folder:
> {code}
> $➔ ll ~/.eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/
> total 36K
> -rw-rw-r-- 1 nboldt nboldt 34K Nov 16 10:54 org.slf4j.api_1.7.2.v20121108-1250.jar
> {code}
> But this plugin is already installed here:
> {code}/opt/rh/rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar{code}
> So even though the connector install doesn't install any new m2e-apt stuff (it's already installed too):
> {code}
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.ui_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.maven.apt.core_1.3.0.201610261805.jar
> /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.maven.apt.feature_1.3.0.201610261805
> {code}
> ... the result of this install is to cause use constrain violations and break the devstudio install.
> A bigger problem occurs in JBDS-4150 when installing Thym or Aerogear features, since a second version of org.apache.httpcomponents.httpclient_4.3.6.v201511171540.jar is installed even though there's already one in the /opt/rh/ install footprint.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months