May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-22411: --------------------------------------- A bug has been opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494256 and a fix has been posted to gerrit. A fix should be present in the Neon RC2 build to be built on Tuesday. > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22376: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Thomas Mäder > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22387) Create New and Noteworthy for 4.4.0.Alpha2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22387?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22387: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Create New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-22387 > URL: https://issues.jboss.org/browse/JBIDE-22387 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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: -------------------------------- Sprint: devex #4 March 2016, devex #115 May 2016 (was: devex #4 March 2016, devex #114 May 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.Alpha3 > > > 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} > Upstream issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=493904 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20687: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Deployed war is NOT the specified war name > ------------------------------------------ > > Key: JBIDE-20687 > URL: https://issues.jboss.org/browse/JBIDE-20687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*. > Sample pom.xml which exibits the issue > {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.glassfish-samples</groupId> > <artifactId>auction</artifactId> > <version>4.0-SNAPSHOT</version> > <packaging>war</packaging> > <name>WebSocket Auction Sample Application</name> > > <dependencies> > <dependency> > <groupId>javax</groupId> > <artifactId>javaee-api</artifactId> > <version>7.0</version> > <scope>provided</scope> > </dependency> > </dependencies> > > <build> > <finalName>websocket-auction</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-war-plugin</artifactId> > <version>2.3</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > <warName>websocket-auction</warName> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22187: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Connection wizard: Should not be able to create duplicate Openshift connections > ------------------------------------------------------------------------------- > > Key: JBIDE-22187 > URL: https://issues.jboss.org/browse/JBIDE-22187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22066: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Server adapter: Stopping debugging of OpenShift application should get application back to normal state. > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha3 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-168) better support cases where the Docker connection is lost [EBZ#471670]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-168?page=com.atlassian.jira.plugin.sy... ] Fred Bricon updated ERT-168: ---------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > better support cases where the Docker connection is lost [EBZ#471670] > --------------------------------------------------------------------- > > Key: ERT-168 > URL: https://issues.jboss.org/browse/ERT-168 > Project: Eclipse Release Train > Issue Type: Enhancement > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Critical > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > this happens on MacOSX after laptop hibernation for example: boot2docker is stopped. > We need to properly inform the user that the connection was lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-169) support for search/pull/push operations on third-party registries [EBZ#471661]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-169?page=com.atlassian.jira.plugin.sy... ] Fred Bricon updated ERT-169: ---------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > support for search/pull/push operations on third-party registries [EBZ#471661] > ------------------------------------------------------------------------------ > > Key: ERT-169 > URL: https://issues.jboss.org/browse/ERT-169 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > We could reuse the nested Search dialog in the "Run Image" wizard for this. > * minimal: have set of registries we can search via > * optimal: use docker demon native search api (without setup) : client.searchImages(term) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22239: -------------------------------- Sprint: devex #115 May 2016 (was: devex #114 May 2016) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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