[ https://issues.jboss.org/browse/JBDS-4128?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-4128: ----------------------------------- So... yes, this is missing. And I'm not sure anything can be done about it. Here's the background: When we made our server have different profiles, to allow to to work with different logic for remote servers or local ones, there were a lot of choices made. One important choice was that we should not force users to create a runtime on the first page, because it may be that a runtime is not necessary. For example, when using a remote server, a local runtime is not necessary. If the user opts to add a runtime, we will add that runtime page into the wizard dynamically. To accomplish this, our server types have the following xml: {code} <serverType hasConfiguration="false" id="org.jboss.ide.eclipse.as.eap.60" launchConfigId="org.jboss.ide.eclipse.as.core.server.startupConfiguration" runtime="false" runtimeTypeId="org.jboss.ide.eclipse.as.runtime.eap.60" supportsRemoteHosts="true"/> {code} The important parts to note here are that: 1) We declare a runtimeTypeId for the server, but, 2) We mark runtime="false". We do this because we have to. If we mark runtime="true", then the runtime will come up as required on the first page of the new server wizard, which we 100% need to avoid. Any fix for this will have to be upstream. I'll see what I can do. -- This message was sent by Atlassian JIRA (v7.2.3#72005)