January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-870) Summarize all features which will be installed in the installer wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-870?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-870: ------------------------------------ Attachment: devstudio-is-installer.png > Summarize all features which will be installed in the installer wizard > ---------------------------------------------------------------------- > > Key: JBTIS-870 > URL: https://issues.jboss.org/browse/JBTIS-870 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > Attachments: devstudio-is-installer.png, inst1.png, inst1.png, jbdsis_installer_summary.png > > > I suggest to summarize all features which will be installed in Summary page. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4258) Could not resolve modules m2e and testng

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4258?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4258. ------------------------------ Verified in 10.3-0.20170131.0115.el7. There is no longer problem with m2e and testng. > Could not resolve modules m2e and testng > ---------------------------------------- > > Key: JBDS-4258 > URL: https://issues.jboss.org/browse/JBDS-4258 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Affects Versions: 10.3.0.AM2 > Environment: RHEL7, HRSCL 2.4. Alpha 1.0 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt > > > Devstudio installed upon rh-eclipse46-base from HRSCL 2.4. Alpha 1.0 (1) fails to start because of bundle conflict. > Base from HRSCL 2.4. newly contains m2e and testng which are also contained in Devstudio. So we probably need to remove m2e and testng from Devstudio. > (1) http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-Alpha... > Log: [^rh-eclipse46-devstudio10.3.log.with_RHSCL_2.4.alfa_1.0.20170126-0712.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4259) Could not resolve module: org.eclipse.recommenders

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4259: ---------------------------------- Summary: Could not resolve module: org.eclipse.recommenders Key: JBDS-4259 URL: https://issues.jboss.org/browse/JBDS-4259 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build, rpm Affects Versions: 10.3.0.GA Environment: RHEL7, RHSCL 2.4 alpha 1.0 Reporter: Lukáš Valach Assignee: Nick Boldt Fix For: 10.3.0.GA Attachments: rh-eclipse46-devstudio10.3.log.20170131-1103.txt I got errors during start of Devstudio 10.3-0.20170131.0115.el7. There are errors like this: {code} org.osgi.framework.BundleException: Could not resolve module: org.eclipse.recommenders.apidocs.rcp [1085] Unresolved requirement: Import-Package: com.google.common.annotations; version="[15.0.0,16.0.0)" {code} Log: [^rh-eclipse46-devstudio10.3.log.20170131-1103.txt] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10116) Issues that affect AS7/EAP integration to tools

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10116?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-10116. --------------------------------- Closing. > Issues that affect AS7/EAP integration to tools > ----------------------------------------------- > > Key: JBIDE-10116 > URL: https://issues.jboss.org/browse/JBIDE-10116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Labels: f2f2012 > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23422: ------------------------------------- [~adietish], debugging code from openshift.js bundle does not handle connection creation - it just passes required parameters like host / port to chromium launch configuration [1]. Connection part is a low level thing that is done in wst.jsdt.chromium bundle [2] [1] https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or... [2] http://git.eclipse.org/c/jsdt/webtools.jsdt.git/tree/bundles/org.eclipse.... > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Jeff MAURY > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23757) Thread deadlock when starting Eclipse

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23757?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23757. --------------------------------- I was never able to reproduce this, but closing since it is hopefully fixed now. Please let us know if you're still experiencing this. This fix is currently available in JBoss Tools 4.4.3.AM2 available from this update site at the moment: http://download.jboss.org/jbosstools/neon/staging/updates/ It will soon appear here (within a week): http://download.jboss.org/jbosstools/neon/development/updates/ Finally, this fix will be included in JBoss Tools 4.4.3.Final release which is to be released on February 21. Once released, it will be available from this update site: http://download.jboss.org/jbosstools/neon/stable/updates/ > Thread deadlock when starting Eclipse > ------------------------------------- > > Key: JBIDE-23757 > URL: https://issues.jboss.org/browse/JBIDE-23757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.Final > Environment: MacOS Sierra, JDK 1.8.0_112 > Reporter: Jon Kranes > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > Steps to reproduce: > * Install latest Eclipse (Neon 4.6.2) (also tested with Spring ToolSuite 3.8.3 with same result) > * Install JBoss AS, Wildfly & EAP Server Tools from JBoss Tools 4.4.2 Final > * Add Wildfly 10.x runtime to Eclipse (tested 10.0 and 10.1 with same results) > * Add Wildfly 10.x server to Eclipse > * Create a default Maven Web App project > * Add the web app project to the Wildfly server > * Exit Eclipse and restart > Eclipse hangs on startup with a thread deadlock. Eclipse "Progress" window shows "Registering Listeners" which never completes and blocks other Eclipse startup tasks. At this point Eclipse cannot exit and must be force-quit. > Thread dump output from jvisualvm shows a thread deadlock: > Found one Java-level deadlock: > ============================= > "Thread-8": > waiting to lock monitor 0x000000011fe4e758 (object 0x0000000782b7aa00, a org.eclipse.wst.server.core.internal.Server), > which is held by "Worker-0" > "Worker-0": > waiting to lock monitor 0x0000000101a566e8 (object 0x0000000782b7aa70, a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager), > which is held by "Thread-8" > Java stack information for the threads listed above: > =================================================== > "Thread-8": > at org.eclipse.wst.server.core.internal.Server.getServerNotificationManager(Server.java:1034) > - waiting to lock <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server) > at org.eclipse.wst.server.core.internal.Server.removeServerListener(Server.java:697) > at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.protectAddManagerAsListeners(UnitedServerListenerManager.java:152) > - locked <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager) > at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.initializeManager(UnitedServerListenerManager.java:81) > at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.access$1(UnitedServerListenerManager.java:73) > at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager$1.run(UnitedServerListenerManager.java:68) > "Worker-0": > at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.addListener(UnitedServerListenerManager.java:109) > - waiting to lock <0x0000000782b7aa70> (a org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager) > at org.jboss.ide.eclipse.as.core.JBossServerCorePlugin.start(JBossServerCorePlugin.java:74) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309) > at org.eclipse.osgi.container.Module.doStart(Module.java:581) > at org.eclipse.osgi.container.Module.start(Module.java:449) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:470) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) > at org.eclipse.wst.server.core.internal.ServerType.createServerDelegate(ServerType.java:91) > at org.eclipse.wst.server.core.internal.Server.getDelegate(Server.java:506) > - locked <0x0000000782b7aa00> (a org.eclipse.wst.server.core.internal.Server) > at org.eclipse.wst.server.core.internal.Server.getChildModules(Server.java:2634) > at org.eclipse.wst.server.core.internal.Server.visitModule(Server.java:3058) > at org.eclipse.wst.server.core.internal.Server.visit(Server.java:3039) > at org.eclipse.wst.server.core.internal.Server.getAllModules(Server.java:1542) > at org.eclipse.wst.server.ui.internal.cnf.ServersView2$3.run(ServersView2.java:189) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Found 1 deadlock. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23641. --------------------------------- I was never able to reproduce this, but closing since it is hopefully fixed now. Please let us know here or in JBIDE-23757 if you're still experiencing this. This fix is currently available in JBoss Tools 4.4.3.AM2 available from this update site at the moment: http://download.jboss.org/jbosstools/neon/staging/updates/ It will soon appear here (within a week): http://download.jboss.org/jbosstools/neon/development/updates/ Finally, this fix will be included in JBoss Tools 4.4.3.Final release which is to be released on February 21. Once released, it will be available from this update site: http://download.jboss.org/jbosstools/neon/stable/updates/ > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Reporter: fede pia > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.3.AM2 > > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23637) AERI report: NPE in CDKRuntimeDetector.exists

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23637?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-23637. --------------------------------- I have added an AERI check that will automatically reopen the jira if problem appears again in new version of the bundle with the same error message. > AERI report: NPE in CDKRuntimeDetector.exists > --------------------------------------------- > > Key: JBIDE-23637 > URL: https://issues.jboss.org/browse/JBIDE-23637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM1 > Reporter: Dmitrii Bocharov > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > https://aer.ctrlflow.com/redhat/reporters#!/problems/584af47be4b0c53b1227... > {noformat} > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.exists(CDKRuntimeDetector.java:106) >  > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.initializeRuntime(CDKRuntimeDetector.java:55) >  > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:78) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:53) >  > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23675) Move org.jboss.tools.openshift.reddeer to jbosstools-openshift/test-framework

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23675?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-23675. ------------------------------ > Move org.jboss.tools.openshift.reddeer to jbosstools-openshift/test-framework > ----------------------------------------------------------------------------- > > Key: JBIDE-23675 > URL: https://issues.jboss.org/browse/JBIDE-23675 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, openshift > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.3.AM2 > > > https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl... > https://github.com/jbosstools/jbosstools-openshift -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4122) Persist environment variables on Mac OS X

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4122?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4122. ----------------------------- If you say so. [~dgolovin]. Closing. > Persist environment variables on Mac OS X > ----------------------------------------- > > Key: JBDS-4122 > URL: https://issues.jboss.org/browse/JBDS-4122 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Environment: Mac OS X > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > > Installer add location for oc cli to PATH env variable. Installer should have util to make persistent changes to any required env variable on Mac OS X. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017