December 2018 - jbosstools-issues

[JBoss JIRA] (JBDS-4713) Fix installer tests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4713?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4713: ----------------------------- Fix Version/s: 12.x (was: 12.10.0.AM1) > Fix installer tests > ------------------- > > Key: JBDS-4713 > URL: https://issues.jboss.org/browse/JBDS-4713 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.GA > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Fix devstudio installer tests on jenkins, suites: > * [BYOE Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Post Installation Tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Devstudio Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4713) Fix installer tests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4713?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4713: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > Fix installer tests > ------------------- > > Key: JBDS-4713 > URL: https://issues.jboss.org/browse/JBDS-4713 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Affects Versions: 12.0.0.GA > Reporter: Vojtech Prusa > Assignee: Ondrej Dockal > Priority: Major > Fix For: 12.x > > > Fix devstudio installer tests on jenkins, suites: > * [BYOE Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Post Installation Tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] > * [Devstudio Installation tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4742) Ensure devstudio can be installed w/ JDK 11 or 12-ea

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBDS-4742?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4742: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > Ensure devstudio can be installed w/ JDK 11 or 12-ea > ---------------------------------------------------- > > Key: JBDS-4742 > URL: https://issues.jboss.org/browse/JBDS-4742 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Major > Fix For: 12.x > > > Now that JDK 11 is the LTS standard, replacing 8, the installer should be updated so it works with 11, and 12-ea too. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26160) Server Adapter: erroneously stays in [Debugging] when you kill the pod

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26160: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Server Adapter: erroneously stays in [Debugging] when you kill the pod > ---------------------------------------------------------------------- > > Key: JBIDE-26160 > URL: https://issues.jboss.org/browse/JBIDE-26160 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.6.0.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Labels: server_adapter > Fix For: 4.11.x > > > steps: > # EXEC: create an application (via ex. nodejs-mongo-persistent template), import the project and create a server adapter for it > # ASSERT: server adapter is created > # EXEC: start the server adapter in Debugging > # ASSERT: sever adapter is in *[Debugging, Synchronized]* state > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is started > # EXEC: in Explorer: select the pod for your service and pick "Delete" > # ASSERT: pod gets deleted and recreated > # ASSERT: select pod and pick "Port Forwarding..." and it states that the forwarding is stopped > Result: > The server adapter still says that is is *[Debugging, Synchronized]*, but debugging is not working any more. Debugging doesn't work any more because the port forwarding was stopped. To have it running again you need to restart the port forwarding for the new pod. > Expected result: > Server adapter should get out of debugging and back into normal run mode *[Started, Synchronized]*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25000: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > 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 > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.11.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* 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} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25000: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > 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 > Priority: Major > Labels: openshift_v3, server_adapter > Fix For: 4.11.x > > Attachments: failed-to-connect-v8-vm.png > > > # ASSERT: have an application running in *[OpenShift Online|https://console.starter-us-east-2.openshift.com/]* 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} > ps. this can be simulated in the CDK, by having everything set and once the pod is up and ithe adapter is in debug, stopping the port forwarding. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24646: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Assignee: Dmitrii Bocharov > Priority: Major > Labels: import_app, openshift_v3 > Fix For: 4.11.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24646) Import application: doesnt check if local branch match

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24646?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24646: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Import application: doesnt check if local branch match > ------------------------------------------------------ > > Key: JBIDE-24646 > URL: https://issues.jboss.org/browse/JBIDE-24646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jan Novak > Assignee: Dmitrii Bocharov > Priority: Major > Labels: import_app, openshift_v3 > Fix For: 4.11.x > > > Importing project from Openshift > * use existing repo > * local repo uses different branch than Openshift > * remote branch isnt locally fetched > * import finishes succesfully > * in local repo is *stil checkouted wrong branch*, without any warnings -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24442: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24442) Import wizard: does nothing if server is not reachable

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24442?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24442: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Import wizard: does nothing if server is not reachable > ------------------------------------------------------ > > Key: JBIDE-24442 > URL: https://issues.jboss.org/browse/JBIDE-24442 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Major > Fix For: 4.11.x > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 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 December 2018