October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26302) Reduce CVE issues in JBT seam bundles

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26302?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26302: ------------------------------- Fix Version/s: 4.10.x (was: 4.9.0.Final) > Reduce CVE issues in JBT seam bundles > ------------------------------------- > > Key: JBIDE-26302 > URL: https://issues.jboss.org/browse/JBIDE-26302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.x > > > Some CVE issues exist in seam bundles: > {code} > org.jboss.tools.cdi.seam.core_1.8.301.v20180807-1920.jar > org.jboss.tools.maven.seam_1.9.1.v20180802-1520.jar{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26302) Reduce CVE issues in JBT seam bundles

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26302?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26302: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.x* > Reduce CVE issues in JBT seam bundles > ------------------------------------- > > Key: JBIDE-26302 > URL: https://issues.jboss.org/browse/JBIDE-26302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.x > > > Some CVE issues exist in seam bundles: > {code} > org.jboss.tools.cdi.seam.core_1.8.301.v20180807-1920.jar > org.jboss.tools.maven.seam_1.9.1.v20180802-1520.jar{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Verification: check if we have fewer CVEs after updating to newer version of fuse 11.1.x: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. #103 > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... vs. build #87 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26162) Better inner loop for OpenShift SpringBoot developers

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26162?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26162: ------------------------------- Fix Version/s: 4.10.x (was: 4.9.0.Final) > Better inner loop for OpenShift SpringBoot developers > ----------------------------------------------------- > > Key: JBIDE-26162 > URL: https://issues.jboss.org/browse/JBIDE-26162 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.10.x > > > Improve DevExp for OpenShift SpringBoot users -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26375) Investigate OpenShift ITests job failures

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26375?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26375: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.0.AM1* and sprint = *devex #156 October 2018* > Investigate OpenShift ITests job failures > ----------------------------------------- > > Key: JBIDE-26375 > URL: https://issues.jboss.org/browse/JBIDE-26375 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.9.0.Final > Environment: CentralCI > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Critical > Fix For: 4.10.0.AM1, 4.10.x > > > Job is failing in last week. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

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

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26160: ------------------------------- Fix Version/s: 4.10.0.AM1 (was: 4.9.0.Final) > 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.10.0.AM1 > > > 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)

7 years, 6 months

1
0
0 / 0

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

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26160?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26160: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.0.AM1* and sprint = *devex #156 October 2018* > 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.10.0.AM1 > > > 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)

7 years, 6 months

1
0
0 / 0

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

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25000: ------------------------------- Fix Version/s: 4.10.0.AM1 (was: 4.9.0.Final) > 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.10.0.AM1 > > 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)

7 years, 6 months

1
0
0 / 0

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

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-25000?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25000: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.0.AM1* and sprint = *devex #156 October 2018* > 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.10.0.AM1 > > 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26358) Implement JMX integration tests

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26358?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26358: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.0.AM1* and sprint = *devex #156 October 2018* > Implement JMX integration tests > ------------------------------- > > Key: JBIDE-26358 > URL: https://issues.jboss.org/browse/JBIDE-26358 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, jmx > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.10.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26339) Update jboss-stacks/minishift.yaml to offer actual container runtime binaries

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26339?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26339: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.10.0.AM1* and sprint = *devex #156 October 2018* > Update jboss-stacks/minishift.yaml to offer actual container runtime binaries > ----------------------------------------------------------------------------- > > Key: JBIDE-26339 > URL: https://issues.jboss.org/browse/JBIDE-26339 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk, qa > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.10.0.AM1 > > > Update offering of downloadable container runtimes in devstudio via jboss-stacks/minishift.yaml and bundled org.jboss.tools.openshift.cdk.server/resources/minishift.yaml. > * minishift 1.22 > * minishift 1.23 > * minishift 1.24 > * cdk 3.6.0 (after its official release) -- This message was sent by Atlassian Jira (v7.12.1#712002)

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