[JBoss JIRA] (JBIDE-22010) For JBIDE 4.3.1.CR1: Prepare for Final/GA
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22010:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA
Key: JBIDE-22010
URL: https://issues.jboss.org/browse/JBIDE-22010
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.3.1.CR1
For JBIDE 4.3.1.CR1: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-3740
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22011) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22011:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [Aerogear]
Key: JBIDE-22011
URL: https://issues.jboss.org/browse/JBIDE-22011
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [Aerogear]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22012) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22012:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [Central Discovery]
Key: JBIDE-22012
URL: https://issues.jboss.org/browse/JBIDE-22012
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [Central Discovery]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22014) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Integration Tests]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22014:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [Integration Tests]
Key: JBIDE-22014
URL: https://issues.jboss.org/browse/JBIDE-22014
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: qa
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [Integration Tests]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22013) For JBIDE 4.3.1.CR1: Prepare for Final/GA [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22013:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [VPE]
Key: JBIDE-22013
URL: https://issues.jboss.org/browse/JBIDE-22013
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [VPE]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22015) For JBIDE 4.3.1.CR1: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22015:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
Key: JBIDE-22015
URL: https://issues.jboss.org/browse/JBIDE-22015
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: build
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22016) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-22016:
----------------------------------
Summary: For JBIDE 4.3.1.CR1: Prepare for Final/GA [Server]
Key: JBIDE-22016
URL: https://issues.jboss.org/browse/JBIDE-22016
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.CR1 [Server]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
[Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
{code}
git checkout jbosstools-4.3.x
{code}
2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[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: Blocker (was: Critical)
> 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, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> 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)
9 years, 11 months
[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:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> 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, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> 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)
9 years, 11 months
[JBoss JIRA] (JBIDE-22009) Rsync failure at server startup
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-22009:
-------------------------------------
Summary: Rsync failure at server startup
Key: JBIDE-22009
URL: https://issues.jboss.org/browse/JBIDE-22009
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Xavier Coulon
Once the server adapter (auto)starts when I get the following error message in my console:
{code}
receiving file list ... done
ROOT.war.deployed
sent 60 bytes received 228 bytes 115.20 bytes/sec
total size is 8498388 speedup is 29508.29
rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
error: exit status 23
{code}
from CLI, I can actually confirm that the {{ROOT.war}} directory exists and is not empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months