[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 updated JBDS-4180:
-----------------------------
Fix Version/s: 10.x
> 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-4181) No valid JDK found
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4181 at 11/16/16 3:21 PM:
------------------------------------------------------------
With which JDK did you START Eclipse? Where's it installed? Do you also have JDK 7 or 9 installed? What's in alternatives for java?
{code}
$➔ alternatives --display java
Current `best' version is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre/bin/java.
$➔ which java
alias java='/usr/bin/java'
/usr/bin/java
$➔ whereis java
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java /opt/jdk1.8.0_102/bin/java /opt/jdk-9-ea+140/bin/java /usr/share/man/man1/java.1.gz
$➔ java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}
What happens if you start eclipse/devstudio using ./eclipse -vm /path/to/java/bin/folder ?
Also, was this installed by update site? installer jar? rpm?
was (Author: nickboldt):
With which JDK did you START Eclipse? Where's it installed? Do you also have JDK 7 or 9 installed? What's in alternatives for java?
{code}
$➔ alternatives --display java
Current `best' version is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre/bin/java.
$➔ which java
alias java='/usr/bin/java'
/usr/bin/java
$➔ whereis java
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java /opt/jdk1.8.0_102/bin/java /opt/jdk-9-ea+140/bin/java /usr/share/man/man1/java.1.gz
$➔ java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}
What happens if you start eclipse/devstudio using ./eclipse -vm /path/to/java/bin/folder ?
> No valid JDK found
> ------------------
>
> Key: JBDS-4181
> URL: https://issues.jboss.org/browse/JBDS-4181
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4181) No valid JDK found
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4181:
-----------------------------
Fix Version/s: 10.x
> No valid JDK found
> ------------------
>
> Key: JBDS-4181
> URL: https://issues.jboss.org/browse/JBDS-4181
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4181) No valid JDK found
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4181:
----------------------------------
With which JDK did you START Eclipse? Where's it installed? Do you also have JDK 7 or 9 installed? What's in alternatives for java?
{code}
$➔ alternatives --display java
Current `best' version is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre/bin/java.
$➔ which java
alias java='/usr/bin/java'
/usr/bin/java
$➔ whereis java
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java /opt/jdk1.8.0_102/bin/java /opt/jdk-9-ea+140/bin/java /usr/share/man/man1/java.1.gz
$➔ java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}
What happens if you start eclipse/devstudio using ./eclipse -vm /path/to/java/bin/folder ?
> No valid JDK found
> ------------------
>
> Key: JBDS-4181
> URL: https://issues.jboss.org/browse/JBDS-4181
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23495) Duplicate proposal for XHTML (JSF)
by Jared González (JIRA)
Jared González created JBIDE-23495:
--------------------------------------
Summary: Duplicate proposal for XHTML (JSF)
Key: JBIDE-23495
URL: https://issues.jboss.org/browse/JBIDE-23495
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf, jsp/jsf/xml/html-source-editing
Affects Versions: 3.2.1.Final
Reporter: Jared González
Priority: Minor
Attachments: eclipse-installed-sw.jpg, eclipse-jboos-tools-jsf-01.jpg
Duplicate proposal from JSF tags
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-987) Update the descrition for SOA category in RH Central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-987?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-987:
-----------------------------
Attachment: jbc1.png
> Update the descrition for SOA category in RH Central
> ----------------------------------------------------
>
> Key: JBTIS-987
> URL: https://issues.jboss.org/browse/JBTIS-987
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
> Attachments: devstudio-is-10.0.0.GA-central.png, jbc1.png
>
>
> At the moment the description for JBoss Integration and SOA Development says
> "Tools related to the development of Integration and SOA applications - includes support for BPEL, BPMN2, Drools, jBPM6 and KIE."
> But the category also contains Fuse and SwitchYard tools.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-987) Update the descrition for SOA category in RH Central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-987?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-987.
------------------------------
Fix Version/s: 10.0.0.GA
Resolution: Done
Corrected in git as well as 10.0.0.GA delivered bits
> Update the descrition for SOA category in RH Central
> ----------------------------------------------------
>
> Key: JBTIS-987
> URL: https://issues.jboss.org/browse/JBTIS-987
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
> Attachments: devstudio-is-10.0.0.GA-central.png, jbc1.png
>
>
> At the moment the description for JBoss Integration and SOA Development says
> "Tools related to the development of Integration and SOA applications - includes support for BPEL, BPMN2, Drools, jBPM6 and KIE."
> But the category also contains Fuse and SwitchYard tools.
--
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 edited comment on JBDS-4162 at 11/16/16 1:14 PM:
------------------------------------------------------------
Note that if you install ANYTHING from Central (or in fact any other update site), the missing dependency will be installed into .eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar because Nice Guy Eclipse sees the missing dep, resolves it from the devstudio TP, and just installs it for you.
So... this is a pretty benign issue. Perhaps we should add the plugin back into the rpm install so it's already installed by default?
was (Author: nickboldt):
Note that if you install ANYTHING from Central (or in fact any other update site), the missing dependency will be installed into .eclipse/org.eclipse.platform_*_linux_gtk_x86_64/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar
So... this is a pretty benign issue. Perhaps we should add the plugin back into the rpm install so it's already installed by default?
> 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