[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 5/18/15 5:42 AM: ------------------------------------------------------------------- When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift: JBIDE-19817 I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml} <!-- application wizard for connections --> <!-- TODO: implement NewApplicationWizard so that it can react to connection changes --> <!-- <extension point="org.jboss.tools.openshift.ui.applicationWizard"> <applicationWizard class="org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizard" connection="org.jboss.tools.openshift.core.connection.Connection"> </applicationWizard> </extension> --> {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! was (Author: adietish): When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml} <!-- application wizard for connections --> <!-- TODO: implement NewApplicationWizard so that it can react to connection changes --> <!-- <extension point="org.jboss.tools.openshift.ui.applicationWizard"> <applicationWizard class="org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizard" connection="org.jboss.tools.openshift.core.connection.Connection"> </applicationWizard> </extension> --> {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)