February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23838) Make DeploymentTest run on Jenkins.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23838: ------------------------------- Fix Version/s: 4.5.0.AM1 > Make DeploymentTest run on Jenkins. > ----------------------------------- > > Key: JBIDE-23838 > URL: https://issues.jboss.org/browse/JBIDE-23838 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM2 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.0.AM1 > > > DeploymentTest is failing. See: > 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... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23869: ------------------------------- Affects Version/s: 4.4.4.AM1 > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.4.4.AM1 > Reporter: Aurélien Pupier > Attachments: image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23866) Integration tests: Arquillian tests are not independent

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23866?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23866: ------------------------------- Fix Version/s: 4.5.0.AM1 > Integration tests: Arquillian tests are not independent > ------------------------------------------------------- > > Key: JBIDE-23866 > URL: https://issues.jboss.org/browse/JBIDE-23866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > > Arquillians tests are now very dependent on each other, rewrite them to have all tests independent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23864) MavenResolver dont find project pom.xml

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23864?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23864: ------------------------------- Fix Version/s: 4.4.4.AM1 > MavenResolver dont find project pom.xml > --------------------------------------- > > Key: JBIDE-23864 > URL: https://issues.jboss.org/browse/JBIDE-23864 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Environment: Eclipse Neon Release 4.6.2 > Reporter: Daniel Reis > Fix For: 4.4.4.AM1 > > > Arquillian plugin cant find pom.xml of the project and dont recognize the classes addeds to archive, displaying many warnings. > The lines that start the warnings are: > File[] files = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().resolve().withTransitivity().asFile(); > return ShrinkWrap.create(WebArchive.class).addAsLibraries(files).addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); > Thanks, > Daniel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23870) Allow edition of Headers for a Jolokia JMX Connection

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23870?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23870: ------------------------------- Fix Version/s: 4.5.0.AM1 > Allow edition of Headers for a Jolokia JMX Connection > ----------------------------------------------------- > > Key: JBIDE-23870 > URL: https://issues.jboss.org/browse/JBIDE-23870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > Attachments: image-2017-02-06-14-07-59-965.png > > > currently headers in Edit JMX Connection are not editable. > !image-2017-02-06-14-07-59-965.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23885) integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23885?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23885: ------------------------------- Fix Version/s: 4.5.0.AM1 > integration test: assert new element "Kind" and in all properties and changed structure in "Build" properties > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23885 > URL: https://issues.jboss.org/browse/JBIDE-23885 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM1 > > > JBIDE-23841: In "Properties" we added a "Kind" property for all resources and changed the structure of the "Build" properties. > The integration tests should assert these changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23422: ------------------------------------- [~adietish] I guess only by changing somehow chromium debugger SocketConnection logic > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Andre Dietisheim > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23817: ---------------------------------------- Assignee: Andre Dietisheim > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23886) Delete Resource: when deleting a resource we should say what resource type is deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23886?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23886: ---------------------------------------- Assignee: Andre Dietisheim > Delete Resource: when deleting a resource we should say what resource type is deleted > ------------------------------------------------------------------------------------- > > Key: JBIDE-23886 > URL: https://issues.jboss.org/browse/JBIDE-23886 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > > When deleting a single resource, we're telling the user that we're deleting a resource. It would be valuable information to tell the user what kind of resource this actually is. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23886) Delete Resource: when deleting a resource we should say what resource type is deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23886?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23886: ------------------------------------- Fix Version/s: 4.4.3.Final > Delete Resource: when deleting a resource we should say what resource type is deleted > ------------------------------------------------------------------------------------- > > Key: JBIDE-23886 > URL: https://issues.jboss.org/browse/JBIDE-23886 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Fix For: 4.4.3.Final > > > When deleting a single resource, we're telling the user that we're deleting a resource. It would be valuable information to tell the user what kind of resource this actually is. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017