October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20730: ------------------------------------- Priority: Minor (was: Major) > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.5.x > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20716 at 10/28/17 4:00 PM: -------------------------------------------------------------------- This isnt the case any more. If you have OpenShift 3 and no server url and then switch to OpenShift 2, the "use default server" checkbox is checked and the server url is filled out. Resolving as OUTDATED was (Author: adietish): This isnt the case any more. If you have OpenShift 3 and no server url and then switch to OpenShift 2, the "use default server" checkbox is checked and the server url is filled out. > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20716. -------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) Assignee: Andre Dietisheim Resolution: Out of Date > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20716. ------------------------------------ > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20716: ------------------------------------------ This isnt the case any more. If you have OpenShift 3 and no server url and then switch to OpenShift 2, the "use default server" checkbox is checked and the server url is filled out. > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20716 > URL: https://issues.jboss.org/browse/JBIDE-20716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.x > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked. > We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20685: ------------------------------------------ JBIDE-21307 and others implemented on-the-fly oc validation. Resolving. > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.5.1.Final > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20685. -------------------------------------- Resolution: Done > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.5.1.Final > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-20685. ------------------------------------ > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.5.1.Final > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20685: ------------------------------------- Fix Version/s: 4.5.1.Final (was: 4.5.x) > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, preferences > Fix For: 4.5.1.Final > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20685: ---------------------------------------- Assignee: Andre Dietisheim > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.5.1.Final > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2017