[
https://issues.jboss.org/browse/JBIDE-25556?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-25556:
-------------------------------------
https://stackoverflow.com/a/35244168
As per the above stackoverflow, it quotes a java issue with more information:
{quote}
Class and resource files previously found in lib/tools.jar and visible only when that file
was added to the class path will now, in a JDK image, be visible via the system class
loader or, in some cases, the bootstrap class loader. The modules containing these files
will not, however, be mentioned in the application class path, i.e., in the value of the
system property java.class.path.
{quote}
This means the normal java9 classpath should have these classes avialable for use
directly, and a tools.jar equivalent doesn't need to be discovered or loaded onto the
classpath for each invocation. I'll be coming up with a patch shortly.
OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK
found
---------------------------------------------------------------------------
Key: JBIDE-25556
URL:
https://issues.jboss.org/browse/JBIDE-25556
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common
Affects Versions: 4.5.2.AM3
Environment: FC27 + OpenJDK9
Reporter: Josef Kopriva
Assignee: Rob Stryker
Fix For: 4.5.x
Error message from error log:
{code:java}
eclipse.buildId=11.2.0.AM3-v20180105-1612-B1822
java.version=9.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -data file:/home/jkopriva/devstudio_B1822-Java9-2/workspace/ -os
linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.common.jdt.debug
Error
Thu Jan 11 10:45:50 CET 2018
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.base/java.util.TimerThread.mainLoop(Timer.java:556)
at java.base/java.util.TimerThread.run(Timer.java:506)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)