March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24140: ------------------------------- Affects Version/s: 4.4.4.AM2 (was: 4.4.1.Final) > Test Failure(s) in JBIDE 4.4.4.AM2 for jst component > ---------------------------------------------------- > > Key: JBIDE-24140 > URL: https://issues.jboss.org/browse/JBIDE-24140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.AM2 > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* > http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... > [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24140: ------------------------------- Description: *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] ----- was: *0 Test Failure(s) in JBIDE 4.4.1.Final for hibernate component:* http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] ----- > Test Failure(s) in JBIDE 4.4.4.AM2 for jst component > ---------------------------------------------------- > > Key: JBIDE-24140 > URL: https://issues.jboss.org/browse/JBIDE-24140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.AM2 > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* > http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... > [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24140: ---------------------------------- Summary: Test Failure(s) in JBIDE 4.4.4.AM2 for jst component Key: JBIDE-24140 URL: https://issues.jboss.org/browse/JBIDE-24140 Project: Tools (JBoss Tools) Issue Type: Task Components: hibernate Affects Versions: 4.4.1.Final Reporter: Nick Boldt Assignee: Koen Aers Priority: Blocker Fix For: 4.4.1.Final *0 Test Failure(s) in JBIDE 4.4.1.Final for hibernate component:* http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... [Search for Test Failure JIRAs in JBIDE 4.4.1.Final for hibernate component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] ----- -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-498) Failure to run image results in Container Not Found [EBZ#514425]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-498?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-498: --------------------------------- Sprint: devex #129 March 2017 Assignee: Jeff Johnston > Failure to run image results in Container Not Found [EBZ#514425] > ---------------------------------------------------------------- > > Key: ERT-498 > URL: https://issues.jboss.org/browse/ERT-498 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 6.0.0, Docker, bzira > Fix For: Oxygen (4.7) > > > Trying to run an invalid command in a container results in a Container Not Found message which is rather cryptic. In addition, any run console is left open for the invalid container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-498) Failure to run image results in Container Not Found [EBZ#514425]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-498: --------------------------------------- Summary: Failure to run image results in Container Not Found [EBZ#514425] Key: ERT-498 URL: https://issues.jboss.org/browse/ERT-498 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Oxygen (4.7) Trying to run an invalid command in a container results in a Container Not Found message which is rather cryptic. In addition, any run console is left open for the invalid container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4320) Show Hyper-V even if it is not detected with link to documentation how to configure and use it with CDK 3

by Robert Kratky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4320?page=com.atlassian.jira.plugin.... ] Robert Kratky commented on JBDS-4320: ------------------------------------- [~dgolovin], there's a short blurb about Hyper-V installation (basically telling users to refer to MS docs) in the CDK Installation Guide: https://access.redhat.com/documentation/en-us/red_hat_container_developme... Is that enough, or do we need something more detailed? Tagging [~bbrock] -- in case changes to CDK docs would be required. > Show Hyper-V even if it is not detected with link to documentation how to configure and use it with CDK 3 > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4320 > URL: https://issues.jboss.org/browse/JBDS-4320 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.4.0.AM1 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1067) Clean update site files for stable/development/staging branch

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1067?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1067: ------------------------------------------ [~pleacu] could you also move all updatesite zip file for the corresponding folders in staging branch, please? > Clean update site files for stable/development/staging branch > ------------------------------------------------------------- > > Key: JBTIS-1067 > URL: https://issues.jboss.org/browse/JBTIS-1067 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.2.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Please clean update site files in stable/development/staging branch so that there are only html and p2 files at > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/ > {code} > and all binaries are in relevant folders such as > {code} > /www_htdocs/devstudio/10.0/stable/updates/integration-stack/10.1.0.GA/ > {code} > Moreover, delete obsolete files from the branch 'staging'. By obsolete files I mean the following > || What we are working on? || Obsolete files || Files I'd like to keep || > | 10.2.0 | 10.0.CR1, 10.0.GA, 10.1.0.CRx, 10.1.0.GA | 10.2.0.CR1, 10.2.0.GA| > EDIT: the branch 'staging' should be cleaned after each official release (once a GA build is publicly available) -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24083: ------------------------------------- Workaround Description: manually add *DEV_MODE* env var to the deployment controller of your node app, wait until the new pod is deployed and restart your server adapter in debugging Workaround: Workaround Exists > 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 > Assignee: Andre Dietisheim > Priority: Critical > Labels: regression > 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24083?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24083: ------------------------------------------ my bad, node debugging is enabled via the *DEV_MODE* env var and *NOT* the *DEBUG* env var! If you manually add the DEV_MODE env var to the replication controller, wait until the new pod is deployed and then restart your adapter in debug mode everything is fine. So we're missing the DEV_MODE. [~jeffmaury] dont we run node apps in DEV_MODE by default? Need to investigate why we're missing DEV_MODE for node > 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 > Assignee: Andre Dietisheim > Priority: Critical > Labels: regression > 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-24139) Cannot "connect debugger" from JMX Navigator if a project is closed

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-24139: --------------------------------------- Summary: Cannot "connect debugger" from JMX Navigator if a project is closed Key: JBIDE-24139 URL: https://issues.jboss.org/browse/JBIDE-24139 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.4.4.AM1, 4.4.3.Final Reporter: Aurélien Pupier {noformat} !ENTRY org.jboss.tools.jmx.ui 4 0 2017-03-29 14:37:58.659 !MESSAGE Resource '/217' is not open. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/217' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144) at org.eclipse.core.internal.resources.Project.hasNature(Project.java:516) at org.jboss.tools.jmx.ui.internal.actions.ConnectDebuggerAction.run(ConnectDebuggerAction.java:59) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) at org.eclipse.equinox.launcher.Main.run(Main.java:1519) at org.eclipse.equinox.launcher.Main.main(Main.java:1492) !SUBENTRY 1 org.eclipse.core.resources 4 372 2017-03-29 14:37:58.659 !MESSAGE Resource '/217' is not open. {noformat} -- 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