April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25053) Attributes restart and to of transition elements stop and next are not validated in Design View

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25053?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25053: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Attributes restart and to of transition elements stop and next are not validated in Design View > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-25053 > URL: https://issues.jboss.org/browse/JBIDE-25053 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Fix For: 4.6.x > > Attachments: Spectacle.M22184.png, job-with-flow.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25017) 1 recurring Test Failure (20+ builds) in JBIDE 4.5.1.AM2 for webservices component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25017?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25017: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > 1 recurring Test Failure (20+ builds) in JBIDE 4.5.1.AM2 for webservices component > ---------------------------------------------------------------------------------- > > Key: JBIDE-25017 > URL: https://issues.jboss.org/browse/JBIDE-25017 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Labels: testfailure > Fix For: 4.6.x > > > *1 Test Failure(s) in JBIDE 4.5.1.AM2 for webservices component:* > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > ----- > {code} > Regression > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 22 builds (Since #671 ) > Took 0.13 sec. > add description > Error Message > Expected: <6> > but: was <10> > Stacktrace > java.lang.AssertionError: > Expected: <6> > but: was <10> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.junit.Assert.assertThat(Assert.java:923) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358) > {code} > -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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.6.x (was: 4.5.x) > 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 > Labels: openshift_v3, server_adapter > Fix For: 4.6.x > > 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.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24997) could org.jboss.tools.ws.jaxrs.core migrate to use lucene 6.1 instead of 3.5?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24997?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24997: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > could org.jboss.tools.ws.jaxrs.core migrate to use lucene 6.1 instead of 3.5? > ----------------------------------------------------------------------------- > > Key: JBIDE-24997 > URL: https://issues.jboss.org/browse/JBIDE-24997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.x > > Attachments: ws.jaxrs.core_lucene3.5.png > > > According to p2, org.jboss.tools.ws.jaxrs.core depends on lucene 3.5. But the latest in Oxygen is 6.1. Could we move up to the latest? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24950) Experience segment.io service

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24950?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24950: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Experience segment.io service > ----------------------------- > > Key: JBIDE-24950 > URL: https://issues.jboss.org/browse/JBIDE-24950 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.5.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: usage > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack200)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24903: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Sonar: report correct test coverage (by using a build that does not use pack200) > --------------------------------------------------------------------------------- > > Key: JBIDE-24903 > URL: https://issues.jboss.org/browse/JBIDE-24903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: build, sonar, test, test-coverage > Fix For: 4.6.x > > Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png > > > Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8% > !image-2017-08-29-14-07-45-069.png! > According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29% > !image-2017-08-29-14-11-01-604.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24976) maven.it.weekly and smoke tests result in yellow balls on multiple OSes

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24976?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24976: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > maven.it.weekly and smoke tests result in yellow balls on multiple OSes > ----------------------------------------------------------------------- > > Key: JBIDE-24976 > URL: https://issues.jboss.org/browse/JBIDE-24976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, maven > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Vojtech Prusa > Fix For: 4.6.x > > Attachments: maven.it.smoke.png, maven.it.weekly.png > > > maven.it.weekly and smoke tests have yellow balls on many OS/JDK combinations. Either we shouldn't run on all these variations, or we should fix the tests :) > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !maven.it.weekly.png|thumbnail! > !maven.it.smoke.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24961) New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24961?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24961: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24961 > URL: https://issues.jboss.org/browse/JBIDE-24961 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25315) Include Fuse CI job update for job configuration update

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25315?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25315: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Include Fuse CI job update for job configuration update > ------------------------------------------------------- > > Key: JBIDE-25315 > URL: https://issues.jboss.org/browse/JBIDE-25315 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.6.x > > Attachments: image-2017-11-02-09-23-36-305.png > > > the CI jobs on Fuse Ci are often not synchronized with modifications done on other jboss tools project such as TARGET_PLATFORM version. > for instance today again: > !image-2017-11-02-09-23-36-305.png|thumbnail! > it would be useful to include the update of the FUSE CI jobs in the process to update the jobs -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25296) IT: server adapter editor: tests should assert that warning about restarting adapter is displayed

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25296?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25296: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > IT: server adapter editor: tests should assert that warning about restarting adapter is displayed > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25296 > URL: https://issues.jboss.org/browse/JBIDE-25296 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests, openshift_v3, server_adapter_editor > Fix For: 4.6.x > > > In JBIDE-25115 the server adapter editor was enhanced to display a warning, telling the user to restart the adapter, once the editor gets dirty -- 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 April 2018