March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25875) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25875: ---------------------------------- Summary: For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation] Key: JBIDE-25875 URL: https://issues.jboss.org/browse/JBIDE-25875 Project: Tools (JBoss Tools) Issue Type: Task Components: foundation Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.3.Final For JBIDE 4.5.3.Final [foundation]: 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.5.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.3.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.71.1.Final {code} mvn clean verify -Dtpc.version=4.71.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.73.0.AM2-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 foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25875) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25875?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25875: ---------------------------------- Assignee: Rob Stryker > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-25875 > URL: https://issues.jboss.org/browse/JBIDE-25875 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [foundation]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25875) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25875?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25875: ------------------------------------ bump up to parent pom version = 4.5.3.Final-SNAPSHOT > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-25875 > URL: https://issues.jboss.org/browse/JBIDE-25875 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [foundation]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25871) Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25871?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25871: ------------------------------------------ [~jeffmaury] weird enough, i an latter try syncing worked, no error complaining about missing rsync or tar. I'm even more baffled. > Server adapter: spring-boot-camel-xml adapter cannot rsync: no rsync nor tar available > -------------------------------------------------------------------------------------- > > Key: JBIDE-25871 > URL: https://issues.jboss.org/browse/JBIDE-25871 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: rsync, server_adapter, springboot > Fix For: 4.5.3.Final > > Attachments: fuse-on-openshift.zip, pod-running.png, rsync-fails.png > > > # ASSERT: have project *camel-ose-springboot-xml* imported to your workspace (from attached archive fuse-on-openshift) > # ASSERT: have a connection to https://console.starter-us-east-2.openshift.com with a project *<username>-stage* > # EXEC: deploy project *camel-ose-springboot-xml* project via fabric-8 maven plugin: > {code} > mvn clean install fabric8:deploy \ > -Dkubernetes.master=https://console.starter-us-east-2.openshift.com \ > -Dkubernetes.namespace=adietish-stage \ > -Dkubernetes.auth.basic.username=<username> \ > -Dkubernetes.auth.basic.password=<password> \ > -Dfabric8.mode=openshift \ > -Dkubernetes.trust.certificates=true \ > -Dfabric8.build.strategy=s2i \ > -Dkubernetes.auth.tryServiceAccount=false \ > -Dfabric8.generator.from=fabric8/s2i-java \ > -Dfabric8.generator.fromMode=docker \ > -Dkubernetes.auth.tryKubeConfig=false > {code} > # ASSERT: you have a pod running for a service *camel-ose-springboot-xml* > !pod-running.png! > # EXEC: create a server adapter for your service *camel-ose-springboot-xml* > # ASSERT: adapter starts automatically and starts to sync local project to OpenShift > Result: > RSync fails, you're told that the container has no strategy for syncing, neither rsync nor tar are available. > !rsync-fails.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25874) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25874: ---------------------------------- Summary: For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid] Key: JBIDE-25874 URL: https://issues.jboss.org/browse/JBIDE-25874 Project: Tools (JBoss Tools) Issue Type: Task Components: aerogear-hybrid Reporter: Nick Boldt Priority: Blocker Fix For: 4.5.3.Final For JBIDE 4.5.3.Final [aerogear-hybrid]: 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.5.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.5.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.5.3.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.71.1.Final {code} mvn clean verify -Dtpc.version=4.71.1.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT {code} mvn clean verify -Dtpc.version=4.73.0.AM2-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 aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25874) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25874?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-25874: ---------------------------------- Assignee: Gorkem Ercan > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid] > ---------------------------------------------------------------------------- > > Key: JBIDE-25874 > URL: https://issues.jboss.org/browse/JBIDE-25874 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [aerogear-hybrid]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25874) For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25874?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25874: ------------------------------------ bump up to parent pom version = 4.5.3.Final-SNAPSHOT > For JBIDE 4.5.3.Final: Prepare for 4.5.3.Final / 11.3.0.GA [aerogear-hybrid] > ---------------------------------------------------------------------------- > > Key: JBIDE-25874 > URL: https://issues.jboss.org/browse/JBIDE-25874 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.5.3.Final > > > For JBIDE 4.5.3.Final [aerogear-hybrid]: 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.5.3.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.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.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.73.0.AM2-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.73.0.AM2-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 aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25679) New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25679?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25679: ------------------------------------------ [~dbocharov] thx! > New Application: OpenShift Online: wizard pops up empty if you create a project right beforehand > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-25679 > URL: https://issues.jboss.org/browse/JBIDE-25679 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.3.Final > > Attachments: image-2018-02-01-10-22-40-265.png > > > # ASSERT: make sure you dont have any project in OpenShift Online (https://console.starter-us-east-1.openshift.com or https://open.paas.redhat.com) > # EXEC: launch new application wizard > # ASSERT: you're prompted to provide the name for a new project that will be created > # EXEC: provide the name, hit "Finish" > Result: > !image-2018-02-01-10-22-40-265.png! > New Application wizard shows up with no project selected nor available in the project combo and thus no templates are listed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25349) Renaming of existing CDK server adapter is not applied everywhere

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25349?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25349: ------------------------------- Sprint: devex #143 January 2018, devex #144 January 2018, devex #147 April 2018 (was: devex #143 January 2018, devex #144 January 2018) > Renaming of existing CDK server adapter is not applied everywhere > ----------------------------------------------------------------- > > Key: JBIDE-25349 > URL: https://issues.jboss.org/browse/JBIDE-25349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.3.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25276?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25276: ------------------------------- Sprint: devex #139 October 2017, devex #143 January 2018, devex #146 March 2018 (was: devex #139 October 2017, devex #143 January 2018, devex #146 March 2018, devex #147 April 2018) > 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

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 March 2018