Oh I didn’t meant we should only have one solution, was just trying to clarify what you are targeting now.
Something worth mentioning is that I am not sure about the need for an archetype, which would require us to go after new product deliverables, maybe investigate what is behind the scenes on their getting started, I don’t see maven being used, at least directly.
Kind of. A single page that would show and tell what I need to do to run a Jakarta EE application on WildFly.
We have something different planned too (on a RFE) but I didn’t had the chance yet to look after that, in short something similar to
https://code.quarkus.io where a website and a maven plugin is used instead of cli and archetype, allowing better functionality and interaction towards building the Maven project. I plan to start looking at this Q4.
That’s not exclusive.
Even if we have a code generator instead of a Maven archetype, we still need a "getting started page » as an entry point.
We can start building this page based on our archetypes and update it whenever we have a code generator.
I suspect than a lot of choices we will make for this user experience could influence what we could achieve with a code generator.
Best regards,
Jeff