Currently if you click on a project on central and you only have WildFly server installed, it will not fulfill the archetype requirement. I suppose this is controlled by stacks.yaml, but I’m not sure - I couldn’t find it there.

The question is whether or not we should allow WildFly to be used as well - both to fulfill the dependency and to be offered when you click Download & Install.
I haven’t tested all of the archetypes, but I tried to use WildFly with some of them and they seemed to work.

Received by email:
Burr:

The last I heard...
we do not yet have the community archetypes to go with wildfly

current archetypes are focused on AS7 & EAP6

Max:

which all should run on WF too so bit surprised we don't fallback to select the highest default example archetype when we have an unknown runtime ?

We actually do fallback (I think). It's just that WildFly is an unknown runtime in this context - you can still create the project, but the first page of the dialog will not show you've fulfilled the requirement.