December 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-26437) Make the Hibernate Tools work with Java 10

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26437?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26437: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > Make the Hibernate Tools work with Java 10 > ------------------------------------------ > > Key: JBIDE-26437 > URL: https://issues.jboss.org/browse/JBIDE-26437 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.11.x > > > This is similar to JBIDE-25553 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26408: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > 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: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: node, server_adapter > Fix For: 4.11.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.12.1#712002)

5 years, 6 months

1
0
0 / 0

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

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26408?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26408: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.x* > 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: Andre Dietisheim > Assignee: Jeff MAURY > Priority: Major > Labels: node, server_adapter > Fix For: 4.11.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.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26406) Update server integration tests to include EAP 7.2 Beta

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26406?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26406: ------------------------------- Fix Version/s: 4.11.x (was: 4.10.0.AM1) > Update server integration tests to include EAP 7.2 Beta > ------------------------------------------------------- > > Key: JBIDE-26406 > URL: https://issues.jboss.org/browse/JBIDE-26406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Major > Labels: EAP, EAP_7, server > Fix For: 4.11.x > > > EAP 7.2 Beta is out since August 26th. We should update the server integration tests so that EAP QE can use our integration tests against it -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26450) Server ITests: Investigate failure in org.jboss.tools.as.itests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26450?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-26450: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.0.AM1* and sprint = *devex #159 December 2018* > Server ITests: Investigate failure in org.jboss.tools.as.itests > --------------------------------------------------------------- > > Key: JBIDE-26450 > URL: https://issues.jboss.org/browse/JBIDE-26450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code:java} > org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes[org.jboss.ide.eclipse.as.wildfly.140]Failed with 0 retries > Error Details > Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > Stack Trace > junit.framework.AssertionFailedError: Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > at org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes(ServerBeanLoaderIntegrationTest.java:69) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24492) Application wizard: Details for custom template are not shown until "Next" is pressed.

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24492: ------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Application wizard: Details for custom template are not shown until "Next" is pressed. > -------------------------------------------------------------------------------------- > > Key: JBIDE-24492 > URL: https://issues.jboss.org/browse/JBIDE-24492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Radim Hopp > Assignee: Josef Kopriva > Priority: Major > Labels: application_wizard > Fix For: 4.11.0.AM1 > > > Almost certainly a regression caused by JBIDE-23473. > I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem? > Screencast: https://youtu.be/uGAmL_sMIXc -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24492) Application wizard: Details for custom template are not shown until "Next" is pressed.

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24492?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24492: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.11.0.AM1* and sprint = *devex #159 December 2018* > Application wizard: Details for custom template are not shown until "Next" is pressed. > -------------------------------------------------------------------------------------- > > Key: JBIDE-24492 > URL: https://issues.jboss.org/browse/JBIDE-24492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Radim Hopp > Assignee: Josef Kopriva > Priority: Major > Labels: application_wizard > Fix For: 4.11.0.AM1 > > > Almost certainly a regression caused by JBIDE-23473. > I know that validation is now bound to pressing "Next" button, but this prevents from showing user the defined resources on first page of wizard in "Details" section. Maybe showing them on second page would solve the problem? > Screencast: https://youtu.be/uGAmL_sMIXc -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26450) Server ITests: Investigate failure in org.jboss.tools.as.itests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26450?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26450: ------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Server ITests: Investigate failure in org.jboss.tools.as.itests > --------------------------------------------------------------- > > Key: JBIDE-26450 > URL: https://issues.jboss.org/browse/JBIDE-26450 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.10.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code:java} > org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes[org.jboss.ide.eclipse.as.wildfly.140]Failed with 0 retries > Error Details > Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > Stack Trace > junit.framework.AssertionFailedError: Expected and actual server beans do not match for server type org.jboss.ide.eclipse.as.wildfly.140 expected:<WildFly> but was:<WildFly> > at org.jboss.tools.as.itests.ServerBeanLoaderIntegrationTest.testServerBeanLoaderFromRuntimes(ServerBeanLoaderIntegrationTest.java:69) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26456) Provision Rhel 8 image with JBDS labels and add it to jenkins

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26456?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26456: ---------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Provision Rhel 8 image with JBDS labels and add it to jenkins > ------------------------------------------------------------- > > Key: JBIDE-26456 > URL: https://issues.jboss.org/browse/JBIDE-26456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Environment: Linux > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins, openstack > Fix For: 4.11.0.AM1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26454) Proxy usage within QE teams, needs and requirements for deploying

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26454?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26454: ---------------------------------- Fix Version/s: 4.11.0.AM1 (was: 4.10.0.AM1) > Proxy usage within QE teams, needs and requirements for deploying > ----------------------------------------------------------------- > > Key: JBIDE-26454 > URL: https://issues.jboss.org/browse/JBIDE-26454 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: quality > Fix For: 4.11.0.AM1 > > > Find out: > * existing solutions within RH > * needs of other teams > * usability of open source proxy technologies/solutions > * usage among different OS -- 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