[
https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-20686 at 6/14/16 8:08 AM:
-------------------------------------------------------------------
[~mlabuda] Isnt the point of being able to restore defaults to override custom settings to
a valid default. A blank field is simply not valid, I would not expect this. Can you argue
why you expect this non-valid value when you choose to return to the defaults.
was (Author: adietish):
Isnt the point of being able to restore defaults to override custom settings to a valid
default. A blank field is simply not valid, I would not expect this. Can you argue why you
expect this non-valid value when you choose to return to the defaults.
Preferences: No OpenShift Client binary warning dialog is shown upon
restoring default preferences
--------------------------------------------------------------------------------------------------
Key: JBIDE-20686
URL:
https://issues.jboss.org/browse/JBIDE-20686
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.CR1
Reporter: Marián Labuda
Labels: openshift_v3, preferences
Fix For: 4.4.x
In OpenShift 3 workbench preference page restoring default setting by clicking on a
button Restore Defaults pops up a warning dialog with title "No OpenShift Client
binary" and text "Could not find the OpenShift binary "oc" on your
path". I would expect that choosing default settings would just clear text field with
oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)