[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25547: ------------------------------------- Description: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is show in the title area !connection-wizard.png! Result: You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences Expected result: Either allow saving the connection even with an invalid oc location or allow to get to the preferences. was: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is show in the title area Result: You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences Expected result: Either allow saving the connection even with an invalid oc location or allow to get to the preferences. -- This message was sent by Atlassian JIRA (v7.5.0#75005)