This is a tracking issue for this upstream bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=514888

Rob's description:
While playing with the changes dropped for Bug 513486, I found a small bug.

When a runtime is optional, the wtp framework does not add the runtime fragment directly. It will only add the server fragment, and assume that the server fragment will introduce the runtime fragment in the workflow as it chooses.

A workflow was discovered where the NewServerWizardFragment is still adding the runtime fragment before the server fragment. Since the server may also be adding that fragment later, it leads to circular behavior because the runtime fragment is in the list of fragments twice. The user will then press next continually but never advance.

Sorry for this bug. It only happens under specific situations.

Workflow:
1) new server wizard, choose server type with optional runtime
2) Go forward, change settings in server fragment, causing server fragment to designate runtime fragment as a child
3) go back to main page of server wizard to change host
4) Change host to 127.0.0.1
5) Press forward, forward, forward, etc. never ends.