November 2016 - jbosstools-issues

[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: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > 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.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21968) Automatically stop server adapters when connection is severed

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21968?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21968: -------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Automatically stop server adapters when connection is severed > ------------------------------------------------------------- > > Key: JBIDE-21968 > URL: https://issues.jboss.org/browse/JBIDE-21968 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk, openshift > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > > It would be nice to automatically stop the server adapter when no longer connected to openshift (i.e. after shutting down CDK) - that way it would reflect the actual state of things. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21364. --------------------------------- Resolution: Rejected We will stick with Runtime.exec(etc) no matter what. The other methods of using a .bat etc do not suit me > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22597) Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22597: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22597 > URL: https://issues.jboss.org/browse/JBIDE-22597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > > When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22668) Deploy Docker Image wizard: should always present the connection page initially (like all other wizards)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22668?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22668: ------------------------------------- Summary: Deploy Docker Image wizard: should always present the connection page initially (like all other wizards) (was: Deploy Docker Image wizard: should be able to skip connection page (or not?)) > Deploy Docker Image wizard: should always present the connection page initially (like all other wizards) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22668 > URL: https://issues.jboss.org/browse/JBIDE-22668 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Dmitrii Bocharov > Labels: connection_wizard, docker, docker_explorer, explorer > Fix For: 4.5.0.AM1 > > > This task was created as a reslut of discussion of [JBIDE-22594|https://issues.jboss.org/browse/JBIDE-22594]. It should be decided whether OS Connection Page worth being skipped or not when opened from Docker Explorer menu item or OS Ecplorer menu item -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22668) Deploy Docker Image wizard: should always present the connection page initially (like all other wizards)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22668?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22668: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Deploy Docker Image wizard: should always present the connection page initially (like all other wizards) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22668 > URL: https://issues.jboss.org/browse/JBIDE-22668 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Dmitrii Bocharov > Labels: connection_wizard, docker, docker_explorer, explorer > Fix For: 4.5.0.AM1 > > > This task was created as a reslut of discussion of [JBIDE-22594|https://issues.jboss.org/browse/JBIDE-22594]. It should be decided whether OS Connection Page worth being skipped or not when opened from Docker Explorer menu item or OS Ecplorer menu item -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21877: ------------------------------------- Please change "Please provide a token" to be more scary / severe, but ONLY in the case of an error... not in the normal wizard > 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: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: screenshot-1.png > > > 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 (v7.2.3#72005)

9 years, 4 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: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > 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: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: screenshot-1.png > > > 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 (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22584: ---------------------------------------- Assignee: Nick Boldt (was: Fred Bricon) > jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22584 > URL: https://issues.jboss.org/browse/JBIDE-22584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, central-update > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Normally, jbosstools-central is built before jbosstools-discovery. > However, running jbosstools-central build for the first time, ran into this: > {code} > 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s] > 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED > 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED > 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Or, this could be a problem w/ bootstrapping values in ide-config.properties? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22584) jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22584?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22584: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > jbosstools-central build and jbosstools-discovery build both depend on the existence of a *-earlyaccess.properties file > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22584 > URL: https://issues.jboss.org/browse/JBIDE-22584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, central-update > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.5.0.AM1 > > > Normally, jbosstools-central is built before jbosstools-discovery. > However, running jbosstools-central build for the first time, ran into this: > {code} > 22:43:51 [INFO] org.jboss.tools.community.central .................. FAILURE [ 0.556 s] > 22:43:51 [INFO] org.jboss.tools.community.central.feature .......... SKIPPED > 22:43:51 [INFO] central.maven.examples.site ........................ SKIPPED > 22:43:52 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:download-maven-plugin:1.2.0:wget (get-earlyaccess-listing) on project org.jboss.tools.community.central: IO Error: Could not get content -> [Help 1] > {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... > Or, this could be a problem w/ bootstrapping values in ide-config.properties? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 November 2016