March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23896?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23896. --------------------------------- Resolution: Done re-opened issue solved in https://issues.jboss.org/browse/JBIDE-23905 > Allow user to choose hypervisor in editor and new server wizard > --------------------------------------------------------------- > > Key: JBIDE-23896 > URL: https://issues.jboss.org/browse/JBIDE-23896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.3.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.4.AM2 > > Attachments: cdk3tp.png > > > Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23961: ------------------------------------ Filed https://issues.jboss.org/browse/JBIDE-24083 in case it's not related to this issue. > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, jbide-23961-restart-1.png, jbide-23961-restart-2.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-24083: ------------------------------- Attachment: jbide-23961-restart-1.png > Debug NodeJS app is broken - Failed to connect to Standalone V8 VM > ------------------------------------------------------------------ > > Key: JBIDE-24083 > URL: https://issues.jboss.org/browse/JBIDE-24083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Priority: Critical > Fix For: 4.4.4.AM2 > > Attachments: jbide-23961-restart-1.png > > > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-24083: ---------------------------------- Summary: Debug NodeJS app is broken - Failed to connect to Standalone V8 VM Key: JBIDE-24083 URL: https://issues.jboss.org/browse/JBIDE-24083 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift, server Affects Versions: 4.4.4.AM1 Reporter: Pavol Srna Fix For: 4.4.4.AM2 {code} java.io.IOException: Failed to get version at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:206) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) ... 9 more Caused by: java.io.IOException: End of stream at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24083) Debug NodeJS app is broken - Failed to connect to Standalone V8 VM

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-24083: ------------------------------- Priority: Critical (was: Major) > Debug NodeJS app is broken - Failed to connect to Standalone V8 VM > ------------------------------------------------------------------ > > Key: JBIDE-24083 > URL: https://issues.jboss.org/browse/JBIDE-24083 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.4.AM1 > Reporter: Pavol Srna > Priority: Critical > Fix For: 4.4.4.AM2 > > > {code} > java.io.IOException: Failed to get version > at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) > at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) > at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) > at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) > at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > Caused by: java.io.IOException: End of stream > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24065) Javascript New and Noteworthy for 4.4.4.AM1

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24065?page=com.atlassian.jira.plugi... ] Victor Rubezhny resolved JBIDE-24065. ------------------------------------- Resolution: Rejected > Javascript New and Noteworthy for 4.4.4.AM1 > --------------------------------------------------- > > Key: JBIDE-24065 > URL: https://issues.jboss.org/browse/JBIDE-24065 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Jeff MAURY > Assignee: Victor Rubezhny > Priority: Critical > > Victor Rubezhny, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Javascript JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Javascript, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Javascript by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24049 #comment Create N&N for Javascript 4.4.4.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Javascript for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24065) Javascript New and Noteworthy for 4.4.4.AM1

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24065?page=com.atlassian.jira.plugi... ] Victor Rubezhny closed JBIDE-24065. ----------------------------------- > Javascript New and Noteworthy for 4.4.4.AM1 > --------------------------------------------------- > > Key: JBIDE-24065 > URL: https://issues.jboss.org/browse/JBIDE-24065 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Jeff MAURY > Assignee: Victor Rubezhny > Priority: Critical > > Victor Rubezhny, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Javascript JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Javascript, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Javascript by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24049 #comment Create N&N for Javascript 4.4.4.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Javascript for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23893) [cdk] follow up on changes to cdk3 for marker file

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23893?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23893. --------------------------------- Resolution: Done The runtime detection is addressed in https://issues.jboss.org/browse/JBIDE-24081 > [cdk] follow up on changes to cdk3 for marker file > -------------------------------------------------- > > Key: JBIDE-23893 > URL: https://issues.jboss.org/browse/JBIDE-23893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.3.Final > Reporter: Rob Stryker > Assignee: Martin Malina > Fix For: 4.4.4.AM2 > > > cdk v3 added marker files with credentials and version information. We need to make use of that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23961: ------------------------------------ stack trace for 'Failed to connect to Standalone V8 VM': {code} java.io.IOException: Failed to get version at org.eclipse.wst.jsdt.chromium.internal.v8native.JavascriptVmImpl.newIOException(JavascriptVmImpl.java:114) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:132) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attach(StandaloneVmImpl.java:79) at org.eclipse.wst.jsdt.chromium.debug.core.model.JavascriptVmEmbedderFactory$4$1.attach(JavascriptVmEmbedderFactory.java:207) at org.eclipse.wst.jsdt.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:74) at org.eclipse.wst.jsdt.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.util.concurrent.ExecutionException: java.io.IOException: End of stream at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:206) at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) ... 9 more Caused by: java.io.IOException: End of stream at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:127) at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl$HandshakeTaks.call(Handshaker.java:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.eclipse.wst.jsdt.chromium.internal.transport.Handshaker$StandaloneV8Impl.perform(Handshaker.java:104) at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ReaderThread.run(SocketConnection.java:158) {code} > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, jbide-23961-restart-1.png, jbide-23961-restart-2.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-23961: ------------------------------- Attachment: jbide-23961-restart-2.png jbide-23961-restart-1.png > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, jbide-23961-restart-1.png, jbide-23961-restart-2.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017