May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24141: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component > ------------------------------------------------------------ > > Key: JBIDE-24141 > URL: https://issues.jboss.org/browse/JBIDE-24141 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.5.0.AM1 > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:* > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2 > {code} > {code} > Failed > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 2 builds (Since Unstable#74 ) > Took 0.15 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} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24185: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24224) Web.xml tree view layout is overlapping

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24224?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24224: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Web.xml tree view layout is overlapping > --------------------------------------- > > Key: JBIDE-24224 > URL: https://issues.jboss.org/browse/JBIDE-24224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.4.AM2 > Environment: Fedora, Eclipse jee-neon (neon.3 based), JBT 4.4.4AM2 > Reporter: Ondrej Dockal > Priority: Minor > Fix For: 4.5.0.AM1 > > Attachments: Screenshot_20170404_182307.png > > > There is somehow overlapping label of Web Descriptor and some other text. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24291) Improve initial loading of JMX Connection tree

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24291: ------------------------------- Fix Version/s: 4.5.0.AM1 > Improve initial loading of JMX Connection tree > ---------------------------------------------- > > Key: JBIDE-24291 > URL: https://issues.jboss.org/browse/JBIDE-24291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > > JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me) > It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server. > For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24222: ------------------------------------- Priority: Critical (was: Major) > CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24222 > URL: https://issues.jboss.org/browse/JBIDE-24222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Environment: macos > xhyve supervisor > cdk3 beta3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.4.Final > > Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24293: ------------------------------- Fix Version/s: 4.5.0.AM1 > Lot of blank lines written to terminal when starting the CDK server > ------------------------------------------------------------------- > > Key: JBIDE-24293 > URL: https://issues.jboss.org/browse/JBIDE-24293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > Attachments: terminalOutputWhenStartingCDK.txt > > > Windows 10 > Version: 10.4.0.AM3 > Build id: AM3-v20170406-1058-B390 > Build date: 20170406-1058 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24293) Lot of blank lines written to terminal when starting the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24293?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-24293: ---------------------------------- Assignee: Rob Stryker > Lot of blank lines written to terminal when starting the CDK server > ------------------------------------------------------------------- > > Key: JBIDE-24293 > URL: https://issues.jboss.org/browse/JBIDE-24293 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Attachments: terminalOutputWhenStartingCDK.txt > > > Windows 10 > Version: 10.4.0.AM3 > Build id: AM3-v20170406-1058-B390 > Build date: 20170406-1058 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24301: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.Final) > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: issues.PNG, issues.txt > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24386) Improve Error Reporting - org.jboss.tools.jmx.jolokia

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24386?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24386: ------------------------------- Fix Version/s: 4.5.0.AM2 > Improve Error Reporting - org.jboss.tools.jmx.jolokia > ----------------------------------------------------- > > Key: JBIDE-24386 > URL: https://issues.jboss.org/browse/JBIDE-24386 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.4.AM3 > Environment: DevStudio 10.4.0.AM3 > jolokia-jvm-1.3.6-agent.jar > Reporter: Tomáš Sedmík > Fix For: 4.5.0.AM2 > > Attachments: jolokia.webm > > > I was unable to connect to a Camel Route via Jolokia. I got the following error in Error Log (see attached video). I have to enable _Do NOT verify SSL Certificates_ in connection details to solve this problem. > The error log could be more descriptive and could notify users where might be a problem. > {code} > eclipse.buildId=10.4.0.GA-v20170427-0526-B16 > java.version=1.8.0_111 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/resources/pluginCustomization.ini > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -pluginCustomization /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/resources/pluginCustomization.ini -data /home/tsedmik/devel/git/jbds-installer/devstudio-is-10.3.0.CR1/target/tmp -clean > org.jboss.tools.jmx.core > Error > Tue May 02 19:14:31 CEST 2017 > Error executing JMX request. > java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Not Found > at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.queryNames(JolokiaMBeanServerConnection.java:140) > at org.jboss.tools.jmx.core.tree.NodeUtils$1.run(NodeUtils.java:58) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.run(JolokiaConnectionWrapper.java:335) > at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:54) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.loadRoot(JolokiaConnectionWrapper.java:141) > at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:192) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pRemoteException: Not Found > at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278) > at org.jolokia.client.J4pClient.execute(J4pClient.java:191) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jboss.tools.jmx.jolokia.internal.connection.JolokiaMBeanServerConnection.queryNames(JolokiaMBeanServerConnection.java:135) > ... 6 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24388) merge integration stack content into discovery site CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24388?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24388: ------------------------------- Description: Today, we only merge IS content into the discovery site builds during staging and release. But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for sample of how to run the merge. was: Today, we only merge IS content into the discovery site builds during staging and release. But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. > merge integration stack content into discovery site CI builds > ------------------------------------------------------------- > > Key: JBIDE-24388 > URL: https://issues.jboss.org/browse/JBIDE-24388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, integration-platform > Affects Versions: 4.4.4.Final, 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Today, we only merge IS content into the discovery site builds during staging and release. > But since this merge operation is now 100% scripted, we could trigger it for all CI builds too. > See https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... for sample of how to run the merge. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 May 2017