[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-984?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-984.
-----------------------------------
Verified with Devstudio IS 10.0.0.GA
!devstudio-is-10.0.0.GA-central.png|thumbnail!
> Update info about Early Access components in RH Central
> -------------------------------------------------------
>
> Key: JBTIS-984
> URL: https://issues.jboss.org/browse/JBTIS-984
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: Devstudio IS 10.0.0.CR4
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
> Attachments: devstudio-is-10.0.0.CR4-central.png, devstudio-is-10.0.0.GA-central.png
>
>
> Devstudio 10.1.0.GA with the following VM args
> -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
> -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
> -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
> says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-984) Update info about Early Access components in RH Central
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-984?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-984:
------------------------------------
Attachment: devstudio-is-10.0.0.GA-central.png
> Update info about Early Access components in RH Central
> -------------------------------------------------------
>
> Key: JBTIS-984
> URL: https://issues.jboss.org/browse/JBTIS-984
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: Devstudio IS 10.0.0.CR4
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA
>
> Attachments: devstudio-is-10.0.0.CR4-central.png, devstudio-is-10.0.0.GA-central.png
>
>
> Devstudio 10.1.0.GA with the following VM args
> -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/devstudio-directory.xml
> -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/
> -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.0.0.CR4/earlyaccess/
> says that the Fuse tooling in on Early Access and is available in 9.x (EDIT: now I noticed that there is "Also available in 9.x" - do we need this?)
--
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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4180:
--------------------------------
Assignee: Rob Stryker (was: Jeff MAURY)
> 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
> 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
>
> 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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4181:
-----------------------------
Component/s: common
> 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
>
> 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 Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4181:
--------------------------------
Assignee: Rob Stryker
> 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] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4180:
--------------------------------
Assignee: Jeff MAURY
> 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
> 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: Jeff MAURY
>
> 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