I can at least prioritize investigating Jakarta EE 9 support. However, I would like to first finish off the Liberty and WildFly support I already started.
That said, I would appreciate it if a few others could chime in with their thoughts here. I have a very hard time convincing myself to try to promote runtimes/versions/releases I really even personally would not use for a work related proof of concept project because they are just not stable/well-documented/well-supported/widely-used enough yet.
As it is, GlassFish and TomEE was a stretch. I ran into very basic bugs with testing, documentation, containerization, etc that would in all reality stopped me from evaluating the runtimes further personally at this time. Now, I do plan to at least report these issues when time permits, but I don’t think most developers can be expected to do that. Indeed, it may turn them away from Jakarta EE if they struggle too much. I think we should not overlook these considerations. It may in the end be unhelpful to what we are trying to accomplish. I wiser path may be to wait until runtime quality improves a bit more?
We don't really want to encourage developers to create new projects on EE 8. And since this is a generator for new projects, we should always support the newer versions.
Not saying that we shouldn't still develop the EE8 archetype, but probably do both...
Ivar