June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24236) cdk3 oc command

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24236: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > cdk3 oc command > --------------- > > Key: JBIDE-24236 > URL: https://issues.jboss.org/browse/JBIDE-24236 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > > After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2 > Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it. > Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24311: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Application wizard: is loading templates even if I go back > ---------------------------------------------------------- > > Key: JBIDE-24311 > URL: https://issues.jboss.org/browse/JBIDE-24311 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4420) DevSuite 1.4 Mac installer Java Install Instructions.

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4420?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4420: ------------------------------ Story Points: 4 > DevSuite 1.4 Mac installer Java Install Instructions. > ----------------------------------------------------- > > Key: JBDS-4420 > URL: https://issues.jboss.org/browse/JBDS-4420 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: DevSuite Installer 1.4, online installer, Mac OS 10.10.5. > Reporter: Robert Terzi > Assignee: Jan Richter > Fix For: 11.0.0.AM2 > > > Running the DevSuite 1.4 online installer on Mac OS, there are several problems with the instructions to install Java: > # There is a link that is shown to "download from +this location+. The link doesn't work and it is impossible to find out where +this location+ is supposed to point to. > # The instructions say that Java 1.8 is required, but they appear under an unchecked OpenJDK 1.8 box. It doesn't make it clear, why you can't just click the OpenJDK box. > # The instructions don't indicate if you need a JDK or JRE. > # It looks like it is trying to get you to download and install Oracle Java 1.8 but doesn't ever say that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

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.AM2 (was: 4.5.0.AM1) > Server adapter: JMX connection is not working for OpenShift instance > --------------------------------------------------------------------- > > 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.AM2 > > > 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)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24411) Explorer: Have to refresh the conenction after correcting credentials in "edit connection" wizard ended

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24411: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Explorer: Have to refresh the conenction after correcting credentials in "edit connection" wizard ended > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24411 > URL: https://issues.jboss.org/browse/JBIDE-24411 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Labels: explorer, openshift_v3 > Fix For: 4.5.0.AM2 > > > Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice) > So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh. > it would be nice to refresh automatically the tree when the connection has been edited -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1122) Update SOARequirements.xsd file

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1122?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1122: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.3.3.Final) > Update SOARequirements.xsd file > ------------------------------- > > Key: JBTIS-1122 > URL: https://issues.jboss.org/browse/JBTIS-1122 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.Final > > Attachments: SOARequirements.xsd > > > I introduced Fuse requirement type (because we want to use camelVersion definition on Fuse on EAP runtimes). Updated XSD file is in the attachment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1122) Update SOARequirements.xsd file

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1122?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1122. ------------------------------------ Resolution: Done > Update SOARequirements.xsd file > ------------------------------- > > Key: JBTIS-1122 > URL: https://issues.jboss.org/browse/JBTIS-1122 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.Final > > Attachments: SOARequirements.xsd > > > I introduced Fuse requirement type (because we want to use camelVersion definition on Fuse on EAP runtimes). Updated XSD file is in the attachment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1121) Create new server requirement for Fuse on EAP

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1121?page=com.atlassian.jira.plugin... ] Andrej Podhradsky updated JBTIS-1121: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.3.3.Final) > Create new server requirement for Fuse on EAP > --------------------------------------------- > > Key: JBTIS-1121 > URL: https://issues.jboss.org/browse/JBTIS-1121 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.Final > > > We need Camel versions defined in JBoss Fuse on EAP modules in server-installer repository. > - create a new server requirement for Fuse on EAP > - adapt config files aligned with the new XSD > - adapt UI tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1121) Create new server requirement for Fuse on EAP

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1121?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1121. ------------------------------------ Resolution: Done > Create new server requirement for Fuse on EAP > --------------------------------------------- > > Key: JBTIS-1121 > URL: https://issues.jboss.org/browse/JBTIS-1121 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.4.3.Final > > > We need Camel versions defined in JBoss Fuse on EAP modules in server-installer repository. > - create a new server requirement for Fuse on EAP > - adapt config files aligned with the new XSD > - adapt UI tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1116) Remove obsolete requirements - ServiceMix, Fabric8

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1116?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1116. ------------------------------------ Resolution: Done > Remove obsolete requirements - ServiceMix, Fabric8 > -------------------------------------------------- > > Key: JBTIS-1116 > URL: https://issues.jboss.org/browse/JBTIS-1116 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.4.3.Final > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Minor > Fix For: 4.4.3.Final > > > Fabric8 and ServiceMix are no longer supported runtimes -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017