[JBoss JIRA] (JBTIS-1153) Missing Fuse category in Devstudio IS standalone installer
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1153:
----------------------------------------
Summary: Missing Fuse category in Devstudio IS standalone installer
Key: JBTIS-1153
URL: https://issues.jboss.org/browse/JBTIS-1153
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 11.0.0.CR2
Reporter: Andrej Podhradsky
Attachments: devstudio_vs_devstudiois.png
The Devstudio installer contains a category for installing Fuse tooling but Devstudio IS installer doesn't. IMHO the Devstudio IS installer should contain everything from Devstudio, wdyt?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4386) Please correct launch configuration so WARN is no longer provided by default
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4386?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-4386.
-------------------------------
I can confirm that both in CLI and in devstudio this happens with EAP 6.4, but not with EAP 7.x. Closing.
> Please correct launch configuration so WARN is no longer provided by default
> ----------------------------------------------------------------------------
>
> Key: JBDS-4386
> URL: https://issues.jboss.org/browse/JBDS-4386
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common
> Affects Versions: 10.3.0.GA
> Environment: DevStudio 10.3, as used with an EAP server.
> Reporter: Rick Wagner
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 11.0.0.AM1
>
>
> Using default settings, an EAP 6.4 (Fuse) server gives the following WARN in the Console view:
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
> Removal of the following param from VM arguments resolves the issue:
> -XX:MaxPermSize=256m
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4180) ClassNotFoundException thrown on devstudio start up
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4180?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-4180.
-------------------------------
Closing. It really seems like something that nobody else has seen and even Marian cannot reproduce.
> 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
> Labels: affects_documentation
> Fix For: 11.0.0.AM1
>
>
> 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)
8 years, 8 months
[JBoss JIRA] (JBTIS-1152) Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final
by Tomas David (JIRA)
Tomas David created JBTIS-1152:
----------------------------------
Summary: Update Drools tests for the new devstudio Drools plugin - 7.0.1.Final
Key: JBTIS-1152
URL: https://issues.jboss.org/browse/JBTIS-1152
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: drools/ jBPM, QE
Affects Versions: 11.0.0.CR2
Environment: DevstudioIS 11.0.0.CR2
Drools plugin 7.0.1.Final
Reporter: Tomas David
Assignee: Tomas David
Fix For: 11.0.0.CR2
The version of drools plugin contains some fixes and the new version of devstudio brings some changes which have to be updated in current drools plugin tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4444) [DevSuite Installer] Move Account step after Confirmation step
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4444?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4444:
--------------------------------
Story Points: 13 (was: 5)
> [DevSuite Installer] Move Account step after Confirmation step
> --------------------------------------------------------------
>
> Key: JBDS-4444
> URL: https://issues.jboss.org/browse/JBDS-4444
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 11.0.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 11.0.0.GA
>
> Attachments: devsuite-installer-1.4.0-workflow.png, devsuite-installer-2.0.0-workflow.png
>
>
> As a user I would like to avoid entering login/password on a first page of installer, so I can explore and see what can be installed and then provide my credentials if I decided to proceed with installation.
> Current workflow is
> !devsuite-installer-1.4.0-workflow.png|thumbnail!
> should be transformed to
> !devsuite-installer-2.0.0-workflow.png|thumbnail!
> This would require to change starting page to show only generic information about DevSuite Installer and whole first page 'Account' should appear after confirmation page in case any of Red Hat Products is selected for installation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months