June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3951: --------------------------------- Component/s: platform-installer (was: installer) > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-221?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-221: ----------------------------- Sprint: devex #116 June 2016 > Exception when debugging with chromium [EBZ#494731] > --------------------------------------------------- > > Key: ERT-221 > URL: https://issues.jboss.org/browse/ERT-221 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: 3.8_RC3, Debug, bzira > Fix For: Neon (4.6) RC3 > > > Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file. > This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever. > Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason. > -- > eclipse.buildId=4.6.0.I20160519-1730 > java.version=1.8.0_77 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.javascript.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product > org.eclipse.wst.jsdt.chromium.debug.core > Error > Fri May 27 11:23:55 CEST 2016 > SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener > java.lang.IllegalStateException: Connection not attached > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101) > at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-221?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-221: ----------------------------- Story Points: 2 > Exception when debugging with chromium [EBZ#494731] > --------------------------------------------------- > > Key: ERT-221 > URL: https://issues.jboss.org/browse/ERT-221 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: 3.8_RC3, Debug, bzira > Fix For: Neon (4.6) RC3 > > > Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file. > This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever. > Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason. > -- > eclipse.buildId=4.6.0.I20160519-1730 > java.version=1.8.0_77 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.javascript.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product > org.eclipse.wst.jsdt.chromium.debug.core > Error > Fri May 27 11:23:55 CEST 2016 > SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener > java.lang.IllegalStateException: Connection not attached > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101) > at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22604: ----------------------------------- Component/s: upstream > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22604: ---------------------------------------- Looks like an upstream issue - https://github.com/dustymabe/vagrant-sshfs/issues/27 > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22176: --------------------------------- Fix Version/s: 4.4.1.Alpha1 > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.1.Alpha1, 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22225: ------------------------------------- Sorry I'm not familiar with that option at all. Have you tried running the OpenShift nodejs-example templates ? After the app is deployed, you can create a server adapter and start it in debug mode, that'll enable DEV_MODE=true. But that'll run on the OpenShift instance, as opposed to what you're doing on the local daemon (from my understanding) > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22176: --------------------------------- Sprint: devex #116 June 2016 > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22176: --------------------------------- Story Points: 10 > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-132: ----------------------------- Sprint: devex #116 June 2016 > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016