May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22313) Deploy Docker Image wizard: need unit tests

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22313?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22313: -------------------------------- Story Points: 6 (was: 16) > Deploy Docker Image wizard: need unit tests > ------------------------------------------- > > Key: JBIDE-22313 > URL: https://issues.jboss.org/browse/JBIDE-22313 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.4.0.Alpha3 > > > There are currently only 2 unit tests for the Deploy Docker Image Wizard in DeployImageWizardModelTest. The wizard is not properly covered by tests yet. -- 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: -------------------------------- Story Points: 3 (was: 8) > 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

[JBoss JIRA] (JBTIS-717) Fix UDF test

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-717: ---------------------------------- Summary: Fix UDF test Key: JBTIS-717 URL: https://issues.jboss.org/browse/JBTIS-717 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.3.0.Final, 4.2.6.Final Reporter: Matus Makovy Assignee: Matus Makovy Fix For: 4.3.1.Final, 4.2.7.Final -- 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: -------------------------------- Story Points: 3 (was: 12) > 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] (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: -------------------------------- Story Points: 2 (was: 10) > 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-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 (was: devex #4 March 2016, devex #115 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-22326) Enable JMX Connections Over "remoting-jmx"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22326?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22326: -------------------------------- Story Points: 2 (was: 15) > Enable JMX Connections Over "remoting-jmx" > ------------------------------------------ > > Key: JBIDE-22326 > URL: https://issues.jboss.org/browse/JBIDE-22326 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Need to add "remoting-jmx" library and support that kind of connection for jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22165: -------------------------------- Story Points: 2 (was: 5) > Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22165 > URL: https://issues.jboss.org/browse/JBIDE-22165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Thomas Mäder > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself... > At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22319: -------------------------------- Story Points: 2 (was: 10) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22321) Use Same ServerHotCodeReplaceListener as for local wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22321?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22321: -------------------------------- Story Points: 2 (was: 10) > Use Same ServerHotCodeReplaceListener as for local wildfly > ---------------------------------------------------------- > > Key: JBIDE-22321 > URL: https://issues.jboss.org/browse/JBIDE-22321 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Thomas Mäder > Fix For: 4.4.x > > > We need to port the fix we have for wildfly to the OpenShiftServer -- 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