May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22257) Remove the e4.ui importer from tP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22257?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-22257: -------------------------------------- Story Points: 1 Assignee: Mickael Istria > Remove the e4.ui importer from tP > --------------------------------- > > Key: JBIDE-22257 > URL: https://issues.jboss.org/browse/JBIDE-22257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > As the org.eclipse.e4.ui.importer is deprecated and its behaviour is now included in org.eclipse.ui.ide, this bundle should be removed from TP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22256) Consume Smart Importer from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22256?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22256: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Consume Smart Importer from upstream > ------------------------------------ > > Key: JBIDE-22256 > URL: https://issues.jboss.org/browse/JBIDE-22256 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > The Smart Importer framework is now directly part of upstream platform.ui. We should remove all references to the e4 fork/sandbox and build only on top of upstream -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22256) Consume Smart Importer from upstream

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22256?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22256: ----------------------------------- Sprint: devex #114 May 2017 > Consume Smart Importer from upstream > ------------------------------------ > > Key: JBIDE-22256 > URL: https://issues.jboss.org/browse/JBIDE-22256 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > The Smart Importer framework is now directly part of upstream platform.ui. We should remove all references to the e4 fork/sandbox and build only on top of upstream -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21983?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21983: -------------------------------- Story Points: 5 Sprint: devex #4 March 2016, devex #114 May 2017 (was: devex #4 March 2016) > 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.Alpha2 > > > 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

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Story Points: 15 > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon (4.6) RC1 > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Story Points: 20 (was: 15) > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon (4.6) RC1 > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Sprint: devex #115 May 2017 > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon (4.6) RC1 > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21680) Trouble installing Hibernate Tools

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21680?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-21680. ------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) Resolution: Done > Trouble installing Hibernate Tools > ---------------------------------- > > Key: JBIDE-21680 > URL: https://issues.jboss.org/browse/JBIDE-21680 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > > Hello, > I was attempting to install the Hibernate Tools for a quick demo but it somehow managed to confuse me.. I probably should know better, but I imagine this could represent quite some population out there. > I headed for the Eclipse marketplace (not the web page but the UI element within Eclipse) after a clean installation of Eclipse Mars update 1. > I search for "Hibernate Tools", and then it seems I have to choose between "Indigo" and "Helios". > TBH I didn't remember that those were Eclipse codename versions, so that's one problem.. I get in trouble trying to install either of course and it takes me a while to figure I need to search for "JBoss Tools" instead.. and probably reinstall my whole IDE to clean the mess. > Searching for "JBoss Tools" isn't great either BTW as the correct result is just third, which means it's not even visible without using the scrollbar.. > I understand we want to push the "JBoss Tools" portfolio but ultimately I think we'd be better off by making sure that people get the right stuff when searching for "Hibernate Tools", as lots of people are accustomed to this name nowadays? > Thanks, > Sanne -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20337) Add unit tests for exploded utility projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20337?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20337: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) Story Points: 3 Sprint: devex #114 May 2017 > Add unit tests for exploded utility projects > -------------------------------------------- > > Key: JBIDE-20337 > URL: https://issues.jboss.org/browse/JBIDE-20337 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Add unit tests for the logic change in JBIDE-15250 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19506: -------------------------------- Story Points: 16 Sprint: devex #114 May 2017 > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha2 > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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