[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 updated JBDS-4180:
-----------------------------
Component/s: foundation
> 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
>
> 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] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21836.
---------------------------------
Canno reproduce neither, closing.
> Preferences: openshift 3 oc location resets to a different/old value on restart
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21836
> URL: https://issues.jboss.org/browse/JBIDE-21836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Critical
> Labels: oc_binary, openshift_v3, preferences
> Fix For: 4.4.2.AM3
>
>
> on start of eclipse new workspace the value is for reason unknown to me set to:
> {code}
> /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc
> {code}
> which does exist, but is old version and publish fails.
> Then I set it to
> {code}
> /usr/local/bin/oc
> {code}
> now publish works.
> Restart eclipse - old value returns and publish starts failing again.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-4176:
--------------------------------------
> This will hide all errors not containing useless-provides
Of course, but I didn't talk about non useless-provides. Anyway...
> the same as addFilter
That's great and the way to go. I didn't study rpmlint much, just skimmed the man page and unfortunately missed those capabilities, I'm sorry.
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 10.x
>
> Attachments: opt-rh-list.2.txt, opt-rh-list.2.txt.sh, opt-rh-list.txt, opt-rh-list.txt.sh
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter (rpmlint.conf):
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
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 Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Marián Labuda updated JBDS-4180:
--------------------------------
Description:
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.
was:
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}
> 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
> 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
>
> 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 Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Marián Labuda updated JBDS-4181:
--------------------------------
Comment: was deleted
(was: Issue JBDS-4180 could be related, need further investigation.)
> 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
> 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-4179) DevStudio installer uses console installation instead of wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Marián Labuda updated JBDS-4179:
--------------------------------
Description:
I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
was:I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Marián Labuda updated JBDS-4179:
--------------------------------
Environment:
openjdk version "1.8.0_102"
OpenJDK Runtime Environment (build 1.8.0_102-b14)
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months