September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7|https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&p...] and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7|https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&p...] and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only [support up to NodeJS 7](https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&... and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Description: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 was: In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See here: https://issues.jboss.org/browse/JBIDE-26408?focusedCommentId=13750500&pag... > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26870?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26870: ------------------------------------- Fix Version/s: 4.14.x > Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools > ---------------------------------------------------------------------- > > Key: JBIDE-26870 > URL: https://issues.jboss.org/browse/JBIDE-26870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.14.x > > > In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. > We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26870) Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools

by André Dietisheim (Jira)

André Dietisheim created JBIDE-26870: ---------------------------------------- Summary: Use wildwestdeveloper/chromedebugger replacing outdated chromedevtools Key: JBIDE-26870 URL: https://issues.jboss.org/browse/JBIDE-26870 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.13.0.AM1 Reporter: André Dietisheim In JBIDE-26408 it has been stated that the chromedevtools only support up to NodeJS 7 and are deprecated/not being worked on any more. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=537907 for more details. We should replace these and use the chrome debugger in wildwestdeveloper instead: see https://github.com/eclipse/wildwebdeveloper/issues/230 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26844) Update WF18 support to WF18 GA

by Mohit Suman (Jira)

[ https://issues.jboss.org/browse/JBIDE-26844?page=com.atlassian.jira.plugi... ] Mohit Suman updated JBIDE-26844: -------------------------------- Story Points: 2 > Update WF18 support to WF18 GA > ------------------------------ > > Key: JBIDE-26844 > URL: https://issues.jboss.org/browse/JBIDE-26844 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.13.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26408) [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26408: ------------------------------------- Comment: was deleted (was: [~jeffmaury] can you please add 4.13.x fixVersion? This needs to be kept open to track upstream developement in Eclipse (or the lack thereof).) > [UPSTREAM] Server adapter: debugging fails for nodejs-mongo-persistent template based application > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-26408 > URL: https://issues.jboss.org/browse/JBIDE-26408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.Final > Environment: cdk-3.6.0+ > Reporter: André Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: node, server_adapter, upstream > Fix For: 4.14.x > > Attachments: change-nodejs-version.png, screenshot-1.png, screenshot-2.png > > > steps: > # ASSERT: have cdk 3.6.0 > # EXEC: create an application based on the *nodejs-mongo-persistent* template, have the application imported to the workspace and the server adapter created for it > # EXEC: start the server adapter > # ASSERT: server adapter is *[Started, Synchronized]* > # EXEC: Restart the adapter into debugging > Result: > You very quickly (the timeout seems very short) get an error dialog telling you that the debugger could not connect. > !screenshot-1.png! > The debugger is therefore stopped, debugging wont work. > !screenshot-2.png! > Trying to restart it reproduces the error that we already have. > In the Eclipse log you'll find the following: > {code} > java.io.IOException: Timed out waiting for handshake > 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:134) > 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:859) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) > at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1026) > at org.eclipse.debug.internal.ui.DebugUIPlugin$2.run(DebugUIPlugin.java:1240) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > Caused by: java.util.concurrent.TimeoutException > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:204) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl.attachImpl(StandaloneVmImpl.java:127) > ... 9 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26818) Installing nodeclipse presents remediation page

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26818?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26818: ------------------------------------- Summary: Installing nodeclipse presents remediation page (was: Installing nodeclipse errors) > Installing nodeclipse presents remediation page > ----------------------------------------------- > > Key: JBIDE-26818 > URL: https://issues.jboss.org/browse/JBIDE-26818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: image-2019-09-09-20-45-46-479.png, installation-cannot-proceed-alternative.png > > > steps: > # ASSERT: have "Software/Update" tab of central editor opened > # EXEC: choose nodeclise and hit "Install/Update" > Result: > Nodeclipse cannot be installed. And error is displayed > !image-2019-09-09-20-45-46-479.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26817) link to "Get involved" shows the page for CAT that was suspended in 2016

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26817?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26817: ------------------------------------ Maybe a deployment of the updated Central page and update to ide-config.properties ? > link to "Get involved" shows the page for CAT that was suspended in 2016 > ------------------------------------------------------------------------ > > Key: JBIDE-26817 > URL: https://issues.jboss.org/browse/JBIDE-26817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > Attachments: image-2019-09-09-21-39-10-326.png, image-2019-09-09-21-40-21-204.png, image-2019-09-11-17-34-37-623.png, issue.png > > > steps: > # ASSERT: have central opened > # EXEC: click on the link "Get involved" > !image-2019-09-09-21-39-10-326.png! > result: > browser is opened displaying the page for the [CAT program|https://tools.jboss.org/cat/] that was suspended in *2016* > !image-2019-09-09-21-40-21-204.png! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23666) Update or remove quickstarts on Central Home Page

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-23666?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23666: ------------------------------------ Given that only warnings are reported, I would be enclined to keep it but as it's based on an old and SNAPSHOTed Maven archetype, I'm fine to remove it > Update or remove quickstarts on Central Home Page > ------------------------------------------------- > > Key: JBIDE-23666 > URL: https://issues.jboss.org/browse/JBIDE-23666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.4.3.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 10.3.0.AM1 > Build id: AM1-v20161225-1238-B6761 > Build date: 20161225-1238 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Critical > Fix For: 4.13.0.Final > > Attachments: central-wizards.png > > > Quickstarts on Central home page are old(links: "HTML5 Project", "AngularJS Forge", "Java EE Web Project"), so when importing these quickstarts, multiple warnings occur: > {code:java} > Description Resource Path Location Type > Build path specifies execution environment JavaSE-1.6. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-as-kitchensink-html5-mobile Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-forge-html5 Build path JRE System Library Problem > Build path specifies execution environment JavaSE-1.7. There are no JREs installed in the workspace that are strictly compatible with this environment. jboss-javaee-webapp Build path JRE System Library Problem > No connection specified for project. No database-specific validation will be performed. jboss-as-kitchensink-html5-mobile JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-forge-html5 JPA Problem > No connection specified for project. No database-specific validation will be performed. jboss-javaee-webapp JPA Problem > No grammar constraints (DTD or XML Schema) referenced in the document. cheatsheet.xml /jboss-forge-html5 line 1 XML Problem > No grammar constraints (DTD or XML Schema) referenced in the document. wro.xml /jboss-as-kitchensink-html5-mobile/src/main/webapp/WEB-INF line 1 XML Problem > {code} > For example HTML5 Project is downloading quickstart "jboss-as-kitchensink-html5-mobile", which is probably https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/33c4600/kit... and this quickstart is requiring Java 1.6. This quickstart can be replaced with newer from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/4aa3caa/kit... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019