October 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26329) Implement CDK runtime detection tests

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26329?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26329. --------------------------------- > Implement CDK runtime detection tests > ------------------------------------- > > Key: JBIDE-26329 > URL: https://issues.jboss.org/browse/JBIDE-26329 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, integration-tests > Affects Versions: 4.9.0.AM3 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.9.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26407) Server adapter: fails with a NPE if there's no oc configured

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26407?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26407: ------------------------------------- Story Points: 1 > Server adapter: fails with a NPE if there's no oc configured > ------------------------------------------------------------- > > Key: JBIDE-26407 > URL: https://issues.jboss.org/browse/JBIDE-26407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Major > Labels: oc_binary, server_adapter > Fix For: 4.10.0.AM1 > > Attachments: screenshot-1.png > > > steps: > # ASSERT: start with a workspace where's no preference that points to an oc binary > # ASSERT: have the connection *NOT* overriding the oc binary location > # EXEC: create a new application (ex. by using the *nodejs-mongo-persistent* template), have the project imported to your workspace and the server adapter created > # EXEC: start the server adapter > Result: > you get an error dialog reporting an NPE > !screenshot-1.png! > The following can be spotted in the Eclipse log: > {code} > java.lang.NullPointerException > at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1022) > at java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1017) > at com.openshift.restclient.OpenShiftContext.put(OpenShiftContext.java:51) > at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:27) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:156) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:148) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:402) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController.access$0(OpenShiftNodejsLaunchController.java:1) > at org.jboss.tools.openshift.js.server.behaviour.OpenShiftNodejsLaunchController$1.onDebugChange(OpenShiftNodejsLaunchController.java:36) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:147) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:96) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > 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.core.LaunchConfiguration.launch(LaunchConfiguration.java:712) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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: ------------------------------------ I did the following test: - get the nodejs-ex code locally - run node --inspect=5858 server.js - create a standalone V8 VM debug conf to localhost:5858 and experienced the same timeout error So I read https://nodejs.org/en/docs/guides/debugging-getting-started/ and discovered --inspect is using another protocol. The one WSDT supports is activated by --debug flag. So this must be a change in the NodeJS OpenShift images. Need to continue to check if we can ask the images to switch back to the old mode > 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.10.0.AM1 > > Attachments: 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)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25276. --------------------------------- Job is green for a long time now, closing. > intermittent test failures in webservices > ----------------------------------------- > > Key: JBIDE-25276 > URL: https://issues.jboss.org/browse/JBIDE-25276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.6.0.Final > > Attachments: ws-intermittent-apr10.png, ws-intermittent-test-failures.png, ws-intermittent-tests.png, ws-intermittent.png > > > Various tests are failing intermittently. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > * All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 12 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 37 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 0.65 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 0.6 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 0.59 sec 1 > org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication 0.1 sec 1 > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.67 sec 2 > Can these be fixed or if not, disabled, so that we can consistently get green builds? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26415) bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version

by Nick Boldt (Jira)

Nick Boldt created JBIDE-26415: ---------------------------------- Summary: bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version Key: JBIDE-26415 URL: https://issues.jboss.org/browse/JBIDE-26415 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.9.0.Final Reporter: Nick Boldt Forgot to bump the version of the poms in jbosstools-build-sites repo, despite using the latest parent pom. Solution: remove all the explicit <version> tags and ensure the version of poms is inherited from parent pom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26415) bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26415?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-26415: ---------------------------------- Assignee: Nick Boldt > bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version > ---------------------------------------------------------------------------------- > > Key: JBIDE-26415 > URL: https://issues.jboss.org/browse/JBIDE-26415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.9.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Major > Fix For: 4.10.0.AM1 > > > Forgot to bump the version of the poms in jbosstools-build-sites repo, despite using the latest parent pom. > Solution: remove all the explicit <version> tags and ensure the version of poms is inherited from parent pom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26415) bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26415?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26415: ------------------------------- Fix Version/s: 4.10.0.AM1 > bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version > ---------------------------------------------------------------------------------- > > Key: JBIDE-26415 > URL: https://issues.jboss.org/browse/JBIDE-26415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.9.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Major > Fix For: 4.10.0.AM1 > > > Forgot to bump the version of the poms in jbosstools-build-sites repo, despite using the latest parent pom. > Solution: remove all the explicit <version> tags and ensure the version of poms is inherited from parent pom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26415) bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26415?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26415: ------------------------------- Priority: Minor (was: Major) > bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version > ---------------------------------------------------------------------------------- > > Key: JBIDE-26415 > URL: https://issues.jboss.org/browse/JBIDE-26415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.9.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.10.0.AM1 > > > Forgot to bump the version of the poms in jbosstools-build-sites repo, despite using the latest parent pom. > Solution: remove all the explicit <version> tags and ensure the version of poms is inherited from parent pom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26415) bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version

by Nick Boldt (Jira)

[ https://issues.jboss.org/browse/JBIDE-26415?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26415: ------------------------------- Issue Type: Task (was: Bug) > bump version of jbosstools-build-sites to 4.10 and inherit from parent pom version > ---------------------------------------------------------------------------------- > > Key: JBIDE-26415 > URL: https://issues.jboss.org/browse/JBIDE-26415 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Affects Versions: 4.9.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.10.0.AM1 > > > Forgot to bump the version of the poms in jbosstools-build-sites repo, despite using the latest parent pom. > Solution: remove all the explicit <version> tags and ensure the version of poms is inherited from parent pom. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26132) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core]

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26132?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26132. --------------------------------- > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [visual-page-editor-core] > ------------------------------------------------------------------------------------ > > Key: JBIDE-26132 > URL: https://issues.jboss.org/browse/JBIDE-26132 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [visual-page-editor-core]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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