April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22242) OpenShift Explorer: Reorganize context menus

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22242?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22242: --------------------------------------- According to the Eclipse guidelines for objects in views (link attached in the end of the description), I think it could/should be following (plus my explanations where it is necessary): *Connection:* {code}New ------------- Refresh Show In ------------- Edit Connection... Delete ------------- Manage Projects... Deploy Docker Image... ------------- Properties{code} *Project:* {code}New ------------- Refresh Show In ------------- Delete ------------- Import Application... Deploy Docker Image... ------------- Properties{code} *Service:* {code}New ------------- Refresh Show In ------------- Edit... Delete ------------- Start Build Deploy Latest Scale ------------- Server Adapter... Import Application... Show Webhooks... ------------- Properties{code} service specific actions/commands are split because of their nature. First part is used for manipulation of an application - start build, deploy latest, scale (= +/- pods) - ordered according to importance/what it does. Second part is more about handling/managing - new server adapter, import app, show webhooks. But maybe there could be found a better way *Pod:* {code}New ------------- Refresh Show In ------------- Delete ------------- Build Log... | (Pod Log... Port Forwarding...) ------------- Properties{code} comments and thoughts are welcomed > OpenShift Explorer: Reorganize context menus > -------------------------------------------- > > Key: JBIDE-22242 > URL: https://issues.jboss.org/browse/JBIDE-22242 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > Labels: explorer, openshift_v3, ux > Fix For: 4.4.0.Alpha2 > > Attachments: connection_cm.png, pod_cm.png, project_cm.png, service_cm.png > > > It would be nice if we would have context menus of OpenShift elements in OpenShift Explorer view a bit reorganized, because at the moment some of them seems to be for me a bit messy (as least context menu of a service). > See screenshots of context menus: > connection > !connection_cm.png! > project > !project_cm.png! > service > !service_cm.png! > pod > !pod_cm.png! > Here is the guideline how should context menus look like > https://wiki.eclipse.org/User_Interface_Guidelines#Context_Menus_2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22118) Application wizard: Should support "builder" images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22118: ------------------------------------- Summary: Application wizard: Should support "builder" images (was: Openshift 3 plugin should support "builder" images) > Application wizard: Should support "builder" images > --------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22165: ------------------------------------- Summary: Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default (was: Check "Add Route" checkbox for exposing services of docker image by default) > 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 > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > 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, 11 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22165: ------------------------------------- Labels: deploy_docker_wizard docker openshift_v3 (was: docker openshift_v3) > 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 > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21877: ------------------------------------- Summary: Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly (was: Make error message shown in OpenShift Explorer for outdated token more user friendly) > Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21877 > URL: https://issues.jboss.org/browse/JBIDE-21877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124) > at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113) > at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69) > at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184) > at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43) > at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154) > at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21877: ------------------------------------- Labels: connection_wizard openshift_v3 (was: connection openshift_v3) > Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21877 > URL: https://issues.jboss.org/browse/JBIDE-21877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124) > at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113) > at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69) > at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184) > at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43) > at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154) > at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22066: ------------------------------------- Summary: Server adapter: Stopping debugging of OpenShift application should get application back to normal state. (was: Stopping debugging of OpenShift application should get application back to normal state.) > 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.Alpha1 > > > 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, 11 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22066: ------------------------------------- Labels: openshift_v3 server_adapter (was: openshift_v3) > 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.Alpha1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22031) Deploy Docker wizard: set message to "Deployment Configuration & Scalability"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22031?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22031: ------------------------------------- Summary: Deploy Docker wizard: set message to "Deployment Configuration & Scalability" (was: Set message to "Deployment Configuration & Scalability" page of Deploy Docker Image wizard) > Deploy Docker wizard: set message to "Deployment Configuration & Scalability" > ----------------------------------------------------------------------------- > > Key: JBIDE-22031 > URL: https://issues.jboss.org/browse/JBIDE-22031 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22031) Deploy Docker wizard: set message to "Deployment Configuration & Scalability"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22031?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22031: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker wizard: set message to "Deployment Configuration & Scalability" > ----------------------------------------------------------------------------- > > Key: JBIDE-22031 > URL: https://issues.jboss.org/browse/JBIDE-22031 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > -- 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 April 2016