June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-1133) Fuse - Fix test ConfigurationsEditorDataFormatsTest

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1133?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1133: ------------------------------------------ Probably this was an issue with the recent changes made in Eclipse. Let's check it once again. > Fuse - Fix test ConfigurationsEditorDataFormatsTest > --------------------------------------------------- > > Key: JBTIS-1133 > URL: https://issues.jboss.org/browse/JBTIS-1133 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE > Affects Versions: 4.5.0.AM1 > Reporter: Andrej Podhradsky > Assignee: Dominik Jelinek > > The test ConfigurationsEditorDataFormatsTest is failing, please fix it. I also suggest to remove the parent class DefaultTest. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24557) Publish Fuse Tools tests (with sources?) to JBT Core Tests site

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24557?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-24557: ---------------------------------------- Approved the PR. You can go on :D Thanks for your efforts. > Publish Fuse Tools tests (with sources?) to JBT Core Tests site > --------------------------------------------------------------- > > Key: JBIDE-24557 > URL: https://issues.jboss.org/browse/JBIDE-24557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM1 > > > If we want to publish Fuse tests into the JBT core tests site, we'll need to apply these: > https://github.com/jbosstools/jbosstools-fuse/pull/989 > https://github.com/jbosstools/jbosstools-build-sites/pull/251 > If accepted I can then add the test SOURCES via a second PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1131) Update drools/jbpm for 4.5.0/11.0.0.release

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1131?page=com.atlassian.jira.plugin... ] Paul Leacu resolved JBTIS-1131. ------------------------------- Fix Version/s: 4.5.0.AM1 Resolution: Done Updated drools/jbpm to 7.0.1.Final. > Update drools/jbpm for 4.5.0/11.0.0.release > ------------------------------------------- > > Key: JBTIS-1131 > URL: https://issues.jboss.org/browse/JBTIS-1131 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM > Affects Versions: 4.5.0.AM1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.5.0.AM1 > > > Update drools/jbpm to 7.0.1.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24557) Publish Fuse Tools tests (with sources?) to JBT Core Tests site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24557?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24557: ------------------------------- Description: If we want to publish Fuse tests into the JBT core tests site, we'll need to apply these: https://github.com/jbosstools/jbosstools-fuse/pull/989 https://github.com/jbosstools/jbosstools-build-sites/pull/251 If accepted I can then add the test SOURCES via a second PR. was: If we want to publish Fuse tests into the JBT core tests site, we'll need to apply these: https://github.com/jbosstools/jbosstools-fuse/pull/983 https://github.com/jbosstools/jbosstools-build-sites/pull/251 > Publish Fuse Tools tests (with sources?) to JBT Core Tests site > --------------------------------------------------------------- > > Key: JBIDE-24557 > URL: https://issues.jboss.org/browse/JBIDE-24557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM1 > > > If we want to publish Fuse tests into the JBT core tests site, we'll need to apply these: > https://github.com/jbosstools/jbosstools-fuse/pull/989 > https://github.com/jbosstools/jbosstools-build-sites/pull/251 > If accepted I can then add the test SOURCES via a second PR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24557) Publish Fuse Tools tests (with sources?) to JBT Core Tests site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24557?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24557: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-fuse/pull/989, https://github.com/jbosstools/jbosstools-build-sites/pull/251 (was: https://github.com/jbosstools/jbosstools-fuse/pull/983, https://github.com/jbosstools/jbosstools-build-sites/pull/251) > Publish Fuse Tools tests (with sources?) to JBT Core Tests site > --------------------------------------------------------------- > > Key: JBIDE-24557 > URL: https://issues.jboss.org/browse/JBIDE-24557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.0.AM1 > > > If we want to publish Fuse tests into the JBT core tests site, we'll need to apply these: > https://github.com/jbosstools/jbosstools-fuse/pull/983 > https://github.com/jbosstools/jbosstools-build-sites/pull/251 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24540: ------------------------------------ Status: waiting on someone from from PL, PgM or PM to decide what to do based on the Goog Analytics data. My professional guess is that we might... a) remove from default-install / deprecate it b) add connector to Central (if not there already) c) remove entirely in about 3-6mo (that is, revisit this discussion for devstudio 11.1 or 11.2, after a few more months of GA traffic data) > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24540 at 6/21/17 2:16 PM: ------------------------------------------------------------- Status: waiting on someone from from PL, PgM or PM to decide what to do based on the Goog Analytics data. My professional guess is that we might... a) remove from default-install / deprecate it b) add connector to Central (if not there already) c) remove entirely in about 3-6mo (that is, revisit this discussion for devstudio 11.1 or 11.2, after a few more months of GA traffic data) Also waiting on confirmation re: which features/plugins are to be moved/deprecated. was (Author: nickboldt): Status: waiting on someone from from PL, PgM or PM to decide what to do based on the Goog Analytics data. My professional guess is that we might... a) remove from default-install / deprecate it b) add connector to Central (if not there already) c) remove entirely in about 3-6mo (that is, revisit this discussion for devstudio 11.1 or 11.2, after a few more months of GA traffic data) > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24560) Server adapter very slow to restart in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24560?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24560: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Server adapter very slow to restart in debug > --------------------------------------------- > > Key: JBIDE-24560 > URL: https://issues.jboss.org/browse/JBIDE-24560 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > When the server adapter has been created and just started, if you restart in debug, it is very slow to restart. It seems to happen only the first time after you created it and started. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24443) Server adapter wizard: cannot distinguish listed items at first sight

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24443?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24443: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Server adapter wizard: cannot distinguish listed items at first sight > --------------------------------------------------------------------- > > Key: JBIDE-24443 > URL: https://issues.jboss.org/browse/JBIDE-24443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.5.0.Final > > Attachments: 2-identical-entries-listed.png, entry-details-deploymentconfig.png, entry-details-service.png > > > steps: > # ASSERT: make sure that you have an application running in OpenShift > # EXEC: launch server adapter wizard > # ASSERT: server adapter wizard pops up listing 2 (at first sight) identical entries for your application > Result: > !2-identical-entries-listed.png! > I cannot easily distinguish the 2 entries that are listed. It's on the 2nd, closer look when comparing the details that I see the difference. The 1st entry is a service, the 2nd is a deployment config. > !entry-details-service.png! > !entry-details-deploymentconfig.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance not using port 8443 for connection url

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24438: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Server adapter: JMX connection is not working for OpenShift instance not using port 8443 for connection url > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24438 > URL: https://issues.jboss.org/browse/JBIDE-24438 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: jmx, jolokia, openshift_v3, server_adapter > Fix For: 4.5.0.Final > > Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4 > > > such as open.paas.redhat.com > {noformat} > java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > 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) > Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out > at org.jolokia.client.J4pClient.mapException(J4pClient.java:330) > at org.jolokia.client.J4pClient.execute(J4pClient.java:198) > 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:311) > ... 4 more > Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out > at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150) > at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) > at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55) > at org.jolokia.client.J4pClient.execute(J4pClient.java:190) > ... 7 more > Caused by: java.net.SocketTimeoutException: connect timed out > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) > at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) > at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) > at java.net.AbstractPlainSocketImpl.connect(Unknown Source) > at java.net.PlainSocketImpl.connect(Unknown Source) > at java.net.SocksSocketImpl.connect(Unknown Source) > at java.net.Socket.connect(Unknown Source) > at sun.security.ssl.SSLSocketImpl.connect(Unknown Source) > at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337) > at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141) > ... 18 more > {noformat} > we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c... > It should not contain the port 8443 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017