June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-177: ----------------------------- Sprint: devex #114 May 2016, devex #116 June 2016 (was: devex #114 May 2016, devex #115 May 2016) > Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998] > --------------------------------------------------------------------------------------------------- > > Key: ERT-177 > URL: https://issues.jboss.org/browse/ERT-177 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC1, General, bzira > Fix For: Neon (4.6) RC3 > > > Created attachment 261462 > Selection related errors > See the screenshot attached for illustration. > Steps for reproduce: > - Create a javascript file with a function and a call to that function. > - Try to invoke content assist: FAIL: no new function appears in CA proposals > - Save, close and open the file again. > - Try to invoke content assist: Now the new function appears in CA proposals > - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration > - FAIL: See wrong text regions highlighted. > - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted. -- 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 Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22225: -------------------------------- Story Points: 30 (was: 15) > 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] (ERT-170) Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-170?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-170: ---------------------------- Story Points: 10 (was: 20) > Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735] > ------------------------------------------------------------------------------------------------- > > Key: ERT-170 > URL: https://issues.jboss.org/browse/ERT-170 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > > The normal scenario for starting a chomium debugger process includes both launching the main js runtime (Node), and also starting the V8 debugger process... > Users will expect the same when terminating (both are killed). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

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

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created JBDS-3951: --------------------------------------- Summary: 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: installer Reporter: Hardy Ferentschik 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] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik reassigned JBDS-3951: --------------------------------------- Assignee: Denis Golovin > 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: 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-170) Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-170?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-170: ---------------------------- Sprint: devex #116 June 2016 (was: devex #115 May 2016) > Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735] > ------------------------------------------------------------------------------------------------- > > Key: ERT-170 > URL: https://issues.jboss.org/browse/ERT-170 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > > The normal scenario for starting a chomium debugger process includes both launching the main js runtime (Node), and also starting the V8 debugger process... > Users will expect the same when terminating (both are killed). -- 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 Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22225: ------------------------------------- This issue is trickier than I expected, due to the fact that the app is running inside the docker container. What I tried so far: - created a docker image with simple node.js app via s2i - https://github.com/sclorg/s2i-nodejs-container - run the image in a DEV_MODE for debugging {code} docker run -p 5858:5858 -p 8080:8080 --env DEV_MODE=true ibuziuk/my-node-app {code} - When I now try to debug the app I'm getting null message on handshake (I guess this is because of bridging network adapter) - The only solution I have found so far for debugging node.js inside docker is to run it with *--net="host"* parameter. {code} docker run --net="host" --env DEV_MODE=true ibuziuk/my-node-app {code} Running docker this way allows to perform handshake and makes debugger work. *--net="host"* gives the container full access to local system services + container will share the host’s network stack and all interfaces from the host will be available to the container. [~adietish], [~fbricon] Do you happen to know if it is possible / allowed to run image with this option ? According to the documentation: {code} Note: --net="host" gives the container full access to local system services such as D-bus and is therefore considered insecure. {code} > 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] (JBTIS-788) Tweek IDEPropertiesSanityTest for SAp integration properties

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-788?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-788. ---------------------------- Fix Version/s: 10.0.0.Alpha1 Resolution: Done Added jboss.discovery.site.integration-stack-sap.feature to the known properties (IDEPropertiesConstants.java) https://github.com/jbosstools/jbosstools-integration-stack/commit/478416b... > Tweek IDEPropertiesSanityTest for SAp integration properties > ------------------------------------------------------------ > > Key: JBTIS-788 > URL: https://issues.jboss.org/browse/JBTIS-788 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: testing > Affects Versions: 10.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 10.0.0.Alpha1 > > > Tweek IDEPropertiesSanityTest for SAp integration properties -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-788) Tweek IDEPropertiesSanityTest for SAp integration properties

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-788: -------------------------------- Summary: Tweek IDEPropertiesSanityTest for SAp integration properties Key: JBTIS-788 URL: https://issues.jboss.org/browse/JBTIS-788 Project: JBoss Tools Integration Stack Issue Type: Task Components: testing Affects Versions: 10.0.0.Alpha1 Reporter: Paul Leacu Assignee: Paul Leacu Tweek IDEPropertiesSanityTest for SAp integration properties -- 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22604: ------------------------------------- VagrantPoller is not being run as other pollers are, in its own thread, repeatedly polling. Instead it is called once before 'vagrant up' and once after 'vagrant up' is completed. There's no need to poll when we know we must wait for the 'vagrant up' process to complete. So we do two synchronous calls only. I've only managed to replicate this once. After the first time, it seems to work as expected. I'll keep investigating. > 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

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