February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21757) Rename JBoss Central into Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21757?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21757: -------------------------------- Fix Version/s: 4.3.1.CR1 > Rename JBoss Central into Red Hat Central > ----------------------------------------- > > Key: JBIDE-21757 > URL: https://issues.jboss.org/browse/JBIDE-21757 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Need to rename JBoss Central into Red Hat Central > - change all text references > - use Red Hat icon for Central tab in Eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21757) Rename JBoss Central into Red Hat Central

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21757: ----------------------------------- Summary: Rename JBoss Central into Red Hat Central Key: JBIDE-21757 URL: https://issues.jboss.org/browse/JBIDE-21757 Project: Tools (JBoss Tools) Issue Type: Task Components: central Affects Versions: 4.3.1.Beta2 Reporter: Fred Bricon Priority: Blocker Need to rename JBoss Central into Red Hat Central - change all text references - use Red Hat icon for Central tab in Eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21757) Rename JBoss Central into Red Hat Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21757?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21757: ----------------------------------- Assignee: Fred Bricon > Rename JBoss Central into Red Hat Central > ----------------------------------------- > > Key: JBIDE-21757 > URL: https://issues.jboss.org/browse/JBIDE-21757 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > > Need to rename JBoss Central into Red Hat Central > - change all text references > - use Red Hat icon for Central tab in Eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21734) Deploying of a docker image from docker explorer has ambiguous connection

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21734?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21734: ----------------------------------------------- [~mlabuda], thank you, I have got it. New pull request is attached. > Deploying of a docker image from docker explorer has ambiguous connection > ------------------------------------------------------------------------- > > Key: JBIDE-21734 > URL: https://issues.jboss.org/browse/JBIDE-21734 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: ambiguous_connection.png > > > When I am trying to deploy a docker image to OpenShift from Docker Explorer view, there is a combo box with listed existing OpenShift connections. If there are more than 1 connection to a specific server, it is not possible to know which one I am selecting (not without knowing its projects and even then they have to be different), because there is no username. The combo box with connections contains only list of server URLs. It could be in format e.g. "username - connection" like we have it on other places. See following screenshot > !ambiguous_connection.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21364: -------------------------------- Fix Version/s: 4.3.2.Final (was: 4.3.1.CR1) > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1, 4.3.2.Final > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21364: ------------------------------------- for now, reading output and parsing works fine. We'll push this off until it's a more pressing need. > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1, 4.3.2.Final > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-54) Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-54?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk resolved ERT-54. ---------------------------- Resolution: Done > Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240] > ---------------------------------------------------------------------------------- > > Key: ERT-54 > URL: https://issues.jboss.org/browse/ERT-54 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Gulp task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-54) Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-54?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk closed ERT-54. -------------------------- Resolution: Done > Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240] > ---------------------------------------------------------------------------------- > > Key: ERT-54 > URL: https://issues.jboss.org/browse/ERT-54 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Gulp task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-55) Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-55?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk resolved ERT-55. ---------------------------- Resolution: Done > Need to add navigation from Project Explorer to Editor for grunt tasks [EBZ#486241] > ----------------------------------------------------------------------------------- > > Key: ERT-55 > URL: https://issues.jboss.org/browse/ERT-55 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Grunt task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21733) Docker connection does not work with CDK build 2016-02-19

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21733?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21733: ------------------------------------- [~hardy.ferentschik] Sorry, but I definitely was not seeing this good behavior. I started initially using only adbinfo when debugging this task, and hadn't even installed the service-manager plugin, and it had repeatedly failed with the raw cdk box. > Docker connection does not work with CDK build 2016-02-19 > --------------------------------------------------------- > > Key: JBIDE-21733 > URL: https://issues.jboss.org/browse/JBIDE-21733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.1.CR1 > > > Today I tried cdk build 2016-02-19 in JBDS 9.1.0.Beta2: > When I started this from JBDS, it worked, but the Docker connection could not be established. > It gives me this error: > {code} > com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:779) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:742) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerImagesContentProvider$1$1.run(DockerImagesContentProvider.java:71) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072) > at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:772) > ... 27 more > Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) > at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) > at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070) > ... 29 more > Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517) > at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293) > at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49) > at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45) > at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523) > at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > 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:1506) > 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:72) > at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469) > ... 20 more > Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed > at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352) > at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260) > at sun.security.validator.Validator.validate(Validator.java:260) > at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) > at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) > at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) > at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1488) > ... 39 more > Caused by: java.security.cert.CertPathValidatorException: signature check failed > at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135) > at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219) > at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) > at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) > at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) > at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347) > ... 45 more > Caused by: java.security.SignatureException: Signature does not match. > at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:449) > at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166) > at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147) > at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125) > ... 50 more > {code} > To be sure, I also tried the other cdk from https://github.com/redhat-developer-tooling/openshift-vagrant and that worked. Then I tried back the official cdk and that didn't work. > I'm pretty sure that this worked for me with the previous build. Not sure what changed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016