[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25873:
----------------------------------------
Summary: Runtime detection: Displayed type CDK 3.2 is confusing
Key: JBIDE-25873
URL: https://issues.jboss.org/browse/JBIDE-25873
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk, openshift
Affects Versions: 4.5.3.AM3
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Attachments: image-2018-03-28-16-26-09-154.png
# ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it
# EXEC: restart your Eclipse
Result:
You get the following dialog when Eclipse is up again:
!image-2018-03-28-16-26-09-154.png!
It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3?
A simple change for the type ex. "CDK 3.2+" would make things so much more obvious.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25873) Runtime detection: Displayed type CDK 3.2 is confusing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25873?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25873:
-------------------------------------
Component/s: runtime-detection
> Runtime detection: Displayed type CDK 3.2 is confusing
> ------------------------------------------------------
>
> Key: JBIDE-25873
> URL: https://issues.jboss.org/browse/JBIDE-25873
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk, openshift, runtime-detection
> Affects Versions: 4.5.3.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Attachments: image-2018-03-28-16-26-09-154.png
>
>
> # ASSERT: make sure that you have a ~/.minishift folder but no server adapter defined for it
> # EXEC: restart your Eclipse
> Result:
> You get the following dialog when Eclipse is up again:
> !image-2018-03-28-16-26-09-154.png!
> It's puzzling for the non-intimate user since one is wondering what detected CDK is, a 3.2 or 3.3?
> A simple change for the type ex. "CDK 3.2+" would make things so much more obvious.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25276) intermittent test failures in webservices
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25276:
-------------------------------
Fix Version/s: 4.5.3.Final
> 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: Jeff MAURY
> Priority: Critical
> Fix For: 4.5.3.Final, 4.5.x
>
> Attachments: ws-intermittent-test-failures.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.5.0#75005)
7 years, 11 months