June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM2 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22613: ------------------------------------- Sprint: devex #123 November 2016, devex #133 Jun 2017 (was: devex #123 November 2016) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.x) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.0.AM2 > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Story Points: 5 > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM1 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24499) Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24499?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24499: ------------------------------------- Story Points: 5 > Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24499 > URL: https://issues.jboss.org/browse/JBIDE-24499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: image-2017-05-23-11-20-07-473.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22613: ------------------------------------- Story Points: 5 (was: 2) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.5.x > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24499) Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24499?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24499: ------------------------------------- Sprint: devex #133 Jun 2017 > Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24499 > URL: https://issues.jboss.org/browse/JBIDE-24499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: image-2017-05-23-11-20-07-473.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24499) Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24499?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-24499: ---------------------------------------- Assignee: Dmitrii Bocharov > Deploy Docker Image wizard: no projects are available if connection wasn't expanded in explorer > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24499 > URL: https://issues.jboss.org/browse/JBIDE-24499 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: image-2017-05-23-11-20-07-473.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Sprint: devex #123 November 2016, devex #133 Jun 2017 (was: devex #123 November 2016, devex #132 May 2017) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24539: ------------------------------------- Sprint: devex #133 Jun 2017 > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM1 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017