March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Description: !server-adapter.png|thumbnail! Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !launch_config.png|thumbnail! Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app. The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace. > Wrong Source Path when creating OS3 Server Adapter for multiple applications > ---------------------------------------------------------------------------- > > Key: JBIDE-21984 > URL: https://issues.jboss.org/browse/JBIDE-21984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, server-adapter.png > > > !server-adapter.png|thumbnail! > Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config. See !launch_config.png|thumbnail! > Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app. > The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Attachment: launch_config.png > Wrong Source Path when creating OS3 Server Adapter for multiple applications > ---------------------------------------------------------------------------- > > Key: JBIDE-21984 > URL: https://issues.jboss.org/browse/JBIDE-21984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: launch_config.png, server-adapter.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21984: ----------------------------------- Attachment: server-adapter.png > Wrong Source Path when creating OS3 Server Adapter for multiple applications > ---------------------------------------------------------------------------- > > Key: JBIDE-21984 > URL: https://issues.jboss.org/browse/JBIDE-21984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: server-adapter.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21984: -------------------------------------- Summary: Wrong Source Path when creating OS3 Server Adapter for multiple applications Key: JBIDE-21984 URL: https://issues.jboss.org/browse/JBIDE-21984 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Alexey Kazakov Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.3.1.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21983: ----------------------------------- Priority: Critical (was: Major) > RuntimeException when trying to see Docker containers/images > ------------------------------------------------------------ > > Key: JBIDE-21983 > URL: https://issues.jboss.org/browse/JBIDE-21983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > > 1. CDK sever adapter -> Show In -> Docker Explorer > 2. Unfold Containers or Images of the rhel-ose CDK Server: > {code} > java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120) > at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95) > at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106) > at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192) > at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70) > at com.spotify.docker.client.DefaultDockerClient.resource(DefaultDockerClient.java:1051) > at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:320) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122) > at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225) > at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135) > ... 12 more > Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266) > at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247) > at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138) > at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109) > at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118) > ... 14 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21983) RuntimeException when trying to see Docker containers/images

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21983: -------------------------------------- Summary: RuntimeException when trying to see Docker containers/images Key: JBIDE-21983 URL: https://issues.jboss.org/browse/JBIDE-21983 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.3.1.CR1 Reporter: Alexey Kazakov Assignee: Xavier Coulon 1. CDK sever adapter -> Show In -> Docker Explorer 2. Unfold Containers or Images of the rhel-ose CDK Server: {code} java.lang.RuntimeException: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:152) at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:120) at javax.ws.rs.core.UriBuilder.newInstance(UriBuilder.java:95) at javax.ws.rs.core.UriBuilder.fromUri(UriBuilder.java:106) at org.glassfish.jersey.client.JerseyWebTarget.<init>(JerseyWebTarget.java:82) at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:192) at org.glassfish.jersey.client.JerseyClient.target(JerseyClient.java:70) at com.spotify.docker.client.DefaultDockerClient.resource(DefaultDockerClient.java:1051) at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:320) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750) at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.ClassNotFoundException: Provider org.glassfish.jersey.internal.RuntimeDelegateImpl could not be instantiated: java.lang.IllegalStateException: No generator was provided and there is no default generator registered at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:122) at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:225) at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:135) ... 12 more Caused by: java.lang.IllegalStateException: No generator was provided and there is no default generator registered at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.internalCreate(ServiceLocatorFactoryImpl.java:266) at org.glassfish.hk2.internal.ServiceLocatorFactoryImpl.create(ServiceLocatorFactoryImpl.java:247) at org.glassfish.jersey.internal.inject.Injections._createLocator(Injections.java:138) at org.glassfish.jersey.internal.inject.Injections.createLocator(Injections.java:109) at org.glassfish.jersey.internal.RuntimeDelegateImpl.<init>(RuntimeDelegateImpl.java:61) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:118) ... 14 more {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3639) Update to official OpenShift client binary

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3639?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3639: -------------------------------------- We are currently using the official v1.1.4 release: https://github.com/openshift/origin/releases/download/v1.1.4/openshift-or... > Update to official OpenShift client binary > ------------------------------------------ > > Key: JBDS-3639 > URL: https://issues.jboss.org/browse/JBDS-3639 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > Once https://github.com/openshift/origin/pull/6127 is part of an upstream release, modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... with the appropriate URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3639) Update to official OpenShift client binary

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3639?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3639: --------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > Update to official OpenShift client binary > ------------------------------------------ > > Key: JBDS-3639 > URL: https://issues.jboss.org/browse/JBDS-3639 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > Once https://github.com/openshift/origin/pull/6127 is part of an upstream release, modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... with the appropriate URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21801) Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-21801: -------------------------------------- The text has been updated as it has been reported in the other issues. > Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup > ----------------------------------------------------------------------------- > > Key: JBIDE-21801 > URL: https://issues.jboss.org/browse/JBIDE-21801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1, 4.3.2.Final > > Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png > > > first technical investigation: > - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%... > and it returns: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <result> > <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText> > <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText> > <customParams> > <param name="company" label="Company" /> > <param name="country" label="Country" > > <options multiple="false"> > </options> > </param> > <param name="downloadURL" label="Downloaded file" > > <options multiple="false"> > <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/> > </options> > </param> > </customParams> > </result> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21947) Docker connection does not work after cdk restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21947?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21947: ------------------------------------- [~hardy.ferentschik] Seems upstream issue is fixed, but what version of service-manager is it in? The linked issue implies it's 0.0.4.1 but is that true? Does our installer need to update or change version in any fashion? > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBIDE-21947 > URL: https://issues.jboss.org/browse/JBIDE-21947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Fix For: 4.3.1.CR1 > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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