[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-21165:
-------------------------------------
[~akazakov], [~gercan] I do believe this one JBIDE-21005 should be rejected if we opt for lauch reimplementation
> Need to improve js tools (npm / bower) launch
> ----------------------------------------------
>
> Key: JBIDE-21165
> URL: https://issues.jboss.org/browse/JBIDE-21165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: nodejs
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available:
> {quote}
> env: node: No such file or directory
> {quote}
> In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process.
> More details can be found here:
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> Basically, this approach kills two birds with one stone:
> 1. No mac os Path issue
> 2. No need to have preferences for node / npm / bower
> Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands
> The plan is:
> - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future)
> - remove irrelevant code with preferences, detectors etc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21166) AJDT can't install against 4.4/Neon
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-21166:
--------------------------------------
Summary: AJDT can't install against 4.4/Neon
Key: JBIDE-21166
URL: https://issues.jboss.org/browse/JBIDE-21166
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: discovery
Affects Versions: 4.4.0.Alpha1
Reporter: Mickael Istria
AJDT fails to install on JBoss Tools 4.4/Eclipse Neon
Various contraint show that AJDT is not compatible with newer JDT.
{code}
!ENTRY org.eclipse.equinox.p2.operations 4 0 2015-11-27 20:08:18.692
!MESSAGE Operation details
!SUBENTRY 1 org.eclipse.equinox.p2.operations 2 10001 2015-11-27 20:08:18.692
!MESSAGE Your original request has been modified.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Mylyn Commons" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Eclipse Git Team Provider" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Mylyn Task-Focused Interface" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.692
!MESSAGE "Eclipse Git Team Provider - Task focused interface" will be ignored because a newer version is already installed.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Atlassian JIRA Connector (Recommended)" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Java implementation of Git" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Mylyn Task List" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.692
!MESSAGE "Mylyn Tasks Connector: Bugzilla" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
!MESSAGE "Mylyn Context Connector: Eclipse IDE" will be ignored because a newer version is already installed.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
!MESSAGE "Mylyn Context Connector: Java Development" will be ignored because a newer version is already installed.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10004 2015-11-27 20:08:18.693
!MESSAGE "Mylyn Context Connector: Team Support" will be ignored because a newer version is already installed.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 1 10006 2015-11-27 20:08:18.693
!MESSAGE "Atlassian Connector for Eclipse Usage Monitoring" is already present because other installed software requires it. It will be added to the installed software list.
!SUBENTRY 2 org.eclipse.equinox.p2.operations 2 10005 2015-11-27 20:08:18.693
!MESSAGE "JBoss Tools Common - Mylyn" will be ignored because it is already installed.
!SUBENTRY 1 org.eclipse.equinox.p2.director 4 10054 2015-11-27 20:08:18.693
!MESSAGE Cannot complete the install because of a conflicting dependency.
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE Software being installed: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE Software currently installed: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
!MESSAGE Only one of the following can be installed at once:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE Java Code Manipulation Functionality 1.5.0.v20120523-1543 (org.eclipse.jdt.core.manipulation 1.5.0.v20120523-1543)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE Java Code Manipulation Functionality 1.7.0.v20150713-1605 (org.eclipse.jdt.core.manipulation 1.7.0.v20150713-1605)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE From: Eclipse IDE for Java EE Developers 4.6.0.20151001-0600 (epp.package.jee 4.6.0.20151001-0600)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE To: org.eclipse.epp.package.jee.feature.feature.group [4.6.0.20151001-0600]
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE From: AspectJ Development Tools Core 2.2.4.e44x-20140516-1000 (org.eclipse.ajdt.core 2.2.4.e44x-20140516-1000)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.693
!MESSAGE To: bundle org.eclipse.jdt.core.manipulation [1.3.0,1.7.0)
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.693
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: EPP Java EE IDE Feature 4.6.0.20151001-0600 (org.eclipse.epp.package.jee.feature.feature.group 4.6.0.20151001-0600)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: org.eclipse.jdt.feature.group 0.0.0
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: Eclipse Java Development Tools 3.11.0.v20150805-2000 (org.eclipse.jdt.feature.group 3.11.0.v20150805-2000)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: Eclipse Java Development Tools 3.12.0.v20150916-2000 (org.eclipse.jdt.feature.group 3.12.0.v20150916-2000)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: Eclipse Java Development Tools 3.12.0.v20151029-1349 (org.eclipse.jdt.feature.group 3.12.0.v20151029-1349)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: org.eclipse.jdt.core.manipulation [1.7.0.v20150713-1605]
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: Spring IDE AJDT Integration (optional) 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.7.0.201506251244-RELEASE)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: org.springframework.ide.eclipse.ajdt.ui.xref [3.7.0.201506251244-RELEASE]
!SUBENTRY 2 org.eclipse.equinox.p2.director 4 1 2015-11-27 20:08:18.694
!MESSAGE Cannot satisfy dependency:
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE From: Spring IDE AOP Xref UI 3.7.0.201506251244-RELEASE (org.springframework.ide.eclipse.ajdt.ui.xref 3.7.0.201506251244-RELEASE)
!SUBENTRY 3 org.eclipse.equinox.p2.director 4 0 2015-11-27 20:08:18.694
!MESSAGE To: package org.eclipse.ajdt.core 0.0.0
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch
by Ilya Buziuk (JIRA)
Ilya Buziuk created JBIDE-21165:
-----------------------------------
Summary: Need to improve js tools (npm / bower) launch
Key: JBIDE-21165
URL: https://issues.jboss.org/browse/JBIDE-21165
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: nodejs
Reporter: Ilya Buziuk
Assignee: Ilya Buziuk
Fix For: 4.4.0.Alpha1
For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available:
{quote}
env: node: No such file or directory
{quote}
In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process.
More details can be found here:
- https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
- https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
Basically, this approach kills two birds with one stone:
1. No mac os Path issue
2. No need to have preferences for node / npm / bower
Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands
The plan is:
- reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future)
- remove irrelevant code with preferences, detectors etc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21158) Improve BaseExplorerContentProvider.loadChildren()
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21158?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-21158:
------------------------------------------
Description:
This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
[~adietish] please take a look at the pull request.
was:
This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
> Improve BaseExplorerContentProvider.loadChildren()
> --------------------------------------------------
>
> Key: JBIDE-21158
> URL: https://issues.jboss.org/browse/JBIDE-21158
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: performance
>
> This method may be called concurrently while children for current parentElement are being loaded. Now for this case implementation calls directly getChildrenFor(parentElement) which loads children in ui thread. So, if by some reason loading children in a separate job took a lot of time, by the same reason this second call in ui thread may hang Eclipse for some time.
> Instead, it seams reasonable just to return the available loading stub as a child, when loading job is completed it will call refresh.
> [~adietish] please take a look at the pull request.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-21159:
-------------------------------------
I don't think so. This started after I updated to the latest version and not even restarting eclipse helps anymore.
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Priority: Blocker
> Labels: connection, openshift_v3
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> 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:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21159:
-------------------------------------
I can connect to that instance just fine. Did it happen after declining the SSL certificate once (JBIDE-21150)?
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Priority: Blocker
> Labels: connection, openshift_v3
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> 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:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21164) cdk server adapter shows error then overridden by adbinfo output
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-21164:
-------------------------------------------
Summary: cdk server adapter shows error then overridden by adbinfo output
Key: JBIDE-21164
URL: https://issues.jboss.org/browse/JBIDE-21164
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
started cdk from server adapter view.
starts up - eventually it fails and output contains my username and password in plain text and some error ...then replaced by output of adbinfo.
A) why was my username/password listed in plain text ? (might be basic vagrant issue not specific to cdk server adapter)
B) why did output of adbinfo override output from vagrant. should this not be appended or handled separately ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21163) cdk server adapter dumps out adbinfo to console
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-21163:
-------------------------------------------
Summary: cdk server adapter dumps out adbinfo to console
Key: JBIDE-21163
URL: https://issues.jboss.org/browse/JBIDE-21163
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
is it intended that if the cdk is running the console shows up with dump that contains:
{quote}
# Set the following environment variables to enable access to the
# docker daemon running inside of the vagrant virtual machine:
export DOCKER_HOST=tcp://10.1.2.2:2376
export DOCKER_CERT_PATH=/Users/max/code/cdk/openshift-vagrant/cdk-v2/.vagrant/machines/default/virtualbox/.docker
export DOCKER_TLS_VERIFY=1
export DOCKER_MACHINE_NAME=9dc5acb
# run following command to configure your shell:
# eval "$(vagrant adbinfo)"
{quote}
it is a bit confusing it pops up with no info and gets to be in front of everything.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months