September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25002) update tests to depend on red deer 2.0 (not 1.2)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25002?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25002: ---------------------------------- Assignee: Rob Stryker > update tests to depend on red deer 2.0 (not 1.2) > ------------------------------------------------ > > Key: JBIDE-25002 > URL: https://issues.jboss.org/browse/JBIDE-25002 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.5.1.AM2 > > > {code} > 21:40:17 [ERROR] Missing requirement: org.jboss.ide.eclipse.archives.ui.test 3.6.111.qualifier > requires 'bundle org.jboss.reddeer.swt 1.2.1' but it could not be found > {code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25002) update tests to depend on red deer 2.0 (not 1.2)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25002: ---------------------------------- Summary: update tests to depend on red deer 2.0 (not 1.2) Key: JBIDE-25002 URL: https://issues.jboss.org/browse/JBIDE-25002 Project: Tools (JBoss Tools) Issue Type: Bug Components: archives Reporter: Nick Boldt {code} 21:40:17 [ERROR] Missing requirement: org.jboss.ide.eclipse.archives.ui.test 3.6.111.qualifier requires 'bundle org.jboss.reddeer.swt 1.2.1' but it could not be found {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20431 at 9/8/17 6:16 PM: ------------------------------------------------------------ I count 50 features here, including 4 from devstudio not in jbosstools: !featureslist-00.png! !featureslist-01.png! Yet on this feature list [1] (pulled from source trees) I get 78 features. So we're still missing 78-46 = 32 features. [1] [^features.txt] I also see things like the vpe and the richfaces feature have the same name. And the jst.feature is called "Jsp Editor Plug-in" but it contains these poorly named plugins: !jst-feature.plugins.png! was (Author: nickboldt): I count 50 features here, including 4 from devstudio not in jbosstools: !featureslist-00.png! !featureslist-01.png! Yet on this feature list (pulled from source trees) I get 78 features. So we're still missing 78-46 = 32 features. I also see things like the vpe and the richfaces feature have the same name. And the jst.feature is called "Jsp Editor Plug-in" but it contains these poorly named plugins: !jst-feature.plugins.png! > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20431: ------------------------------------ I count 50 features here, including 4 from devstudio not in jbosstools: !featureslist-00.png! !featureslist-01.png! Yet on this feature list (pulled from source trees) I get 78 features. So we're still missing 78-46 = 32 features. I also see things like the vpe and the richfaces feature have the same name. And the jst.feature is called "Jsp Editor Plug-in" but it contains these poorly named plugins: !jst-feature.plugins.png! > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20431: ------------------------------- Attachment: features.txt > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20431: ------------------------------- Attachment: jst-feature.plugins.png > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20431: ------------------------------- Attachment: featureslist-01.png featureslist-00.png > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.1.AM2 > > Attachments: features.txt, featureslist-00.png, featureslist-01.png, jst-feature.plugins.png > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25000 at 9/8/17 6:04 PM: ------------------------------------------------------------------ Ideally we'd have the debugger to try a few times (with a timeout) before erroring. My workaround for this would be to try to reach the debugger socket and only launch the debugger launch config once this succeeds. [~ibuziuk] do you know how to make the chromium debugger try to connect a few times (with a timeout) or how to check if nodejs is (up and) listening on the debugger port? (for the understanding how we do things: to enable debugging we set env vars in the dc which causes a new pod to be created. We wait for the pod to be running, but not for nodejs to be running) was (Author: adietish): Ideally we'd have the debugger to try a few times (with a timeout) before erroring. My workaround for this would be to try to reach the debugger socket and only launch the debugger launch config once this succeeds. [~ibuziuk] do you know how to make the chromium debugger try a few times (with a timeout) or how to check if nodejs is (up and) listening on the debugger port? > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.1.AM2 > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.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:56) > 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25000) Server adapter: starting into debugging fails initially (succeeds on a latter try)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-25000 at 9/8/17 6:01 PM: ------------------------------------------------------------------ This very much looks like we're trying to connect to nodejs when it's not fully up yet. Implying this is that the issue wont happen in the 2nd restart. The same is suggested by the fact that it also doesn't happen if you start the adapter in debug while the app already is in debug mode (check env vars in the service/dc, verify that it has devmode set to "true" and the debug port to some numerical value). We're waiting for the pod to run, but not for nodejs to be up. was (Author: adietish): This very much looks like we're trying to connect to nodejs when it's not fully up yet bcs the issue wont happen in the 2nd restart (mostly). The same is suggested since the issue wont happen you start the adapter in debug when the app is in debug mode already (check env vars in the service/dc, verify that it has devmode set to "true" and the debug port to some numerical value). We're waiting for the pod to run, but not for nodejs to be up. > Server adapter: starting into debugging fails initially (succeeds on a latter try) > ---------------------------------------------------------------------------------- > > Key: JBIDE-25000 > URL: https://issues.jboss.org/browse/JBIDE-25000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.5.1.AM2 > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in OpenShift based on the "nodejs-mongo-persistent" template > # ASSERT: have a server adapter for it > # EXEC/ASSERT: have the adapter started in non-debugging/normal mode > # EXEC: restart the adapter debugging > Result: > !failed-to-connect-v8-vm.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:56) > 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)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4542) remove duplicate entries from target platforms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4542?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4542: ----------------------------- Parent: JBDS-4530 Issue Type: Sub-task (was: Feature Request) > remove duplicate entries from target platforms > ---------------------------------------------- > > Key: JBDS-4542 > URL: https://issues.jboss.org/browse/JBDS-4542 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 11.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM3 > > Attachments: 4.71.0.AM2-SNAPSHOT_vs_4.71.0.AM3-SNAPSHOT_considerVersions.p2diff.sorted.txt, multiple.uis.list.txt > > > Current 4.60.0.Final TP contains duplicates of these IUs: > * org.eclipse.m2e.model.edit > * org.eclipse.egit.ui.smartimport > * ...others? > Duplication should be avoided. See also JBIDE-22611. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017