[JBoss JIRA] (JBIDE-25556) OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-25556:
-------------------------------------
Summary: 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
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)
8 years, 2 months
[JBoss JIRA] (JBIDE-25554) Fuse tests are failing on dev-platform
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBIDE-25554:
-----------------------------------------
Summary: Fuse tests are failing on dev-platform
Key: JBIDE-25554
URL: https://issues.jboss.org/browse/JBIDE-25554
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, fusetools
Affects Versions: 4.5.2.AM2
Reporter: Andrej Podhradsky
Fix For: 4.5.x
Attachments: log.txt
The job jbosstools-fuse_PullRequest is failing on dev-platform but it passes on fusesource. See the attached log file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4642) JDK9 Certification
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ]
Pavol Srna commented on JBDS-4642:
----------------------------------
[~nickboldt], there is no more work to plan on the subtasks other then running the tests with jdk9 and see if the component meet the criteria or not. So it maybe does not matter if they inherit the sprint from this epic. But we can convert them to subtasks if you wish, i'm not against.
If we find issues running some component with jdk9, then separate jiras will be filed (e.g. as the linked hibernate one above). For these issues it is important to plan them accordingly in the sprint, because they require some DEV work and can take significant time to resolve.
> JDK9 Certification
> ------------------
>
> Key: JBDS-4642
> URL: https://issues.jboss.org/browse/JBDS-4642
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: build
> Reporter: Pavol Srna
> Fix For: 11.x
>
>
> This is an epic for tracking JDK9 Devstudio Certification.
> All components need to be retested (run) with JDK9. Please link issues found here.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBDS-4642) JDK9 Certification
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4642:
----------------------------------
I'm curious why this Epic was created with subtasks (which will inherit the parent's sprint) rather than creating issues IN the epic (which can be assigned to different sprints).
If the above doesn't matter, ignore me. If it does, the subtasks should all be converted to full issues / tasks, then linked to this epic.
> JDK9 Certification
> ------------------
>
> Key: JBDS-4642
> URL: https://issues.jboss.org/browse/JBDS-4642
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: build
> Reporter: Pavol Srna
> Fix For: 11.x
>
>
> This is an epic for tracking JDK9 Devstudio Certification.
> All components need to be retested (run) with JDK9. Please link issues found here.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months