Hi,

In order to make progress on this feature and agree on its content, I opened WFLY-18428[1] and its
wildfly-proposal at [2].

You can try this by installing locally Darran’s archetype (as explained in [2]) and then follow the steps at http://jmesnil.github.io/wildfly.org/getstarted/

The intent of this is really to « get started » with WildFly. This will not cover all that can be achieved with WildFly but gives just enough for a new or existing users to try WildFly in a matter of minutes and start writing their code with it.

Best regards,
Jeff


[1] https://issues.redhat.com/browse/WFLY-18428
[2] https://github.com/wildfly/wildfly-proposals/pull/536

On 10 Aug 2023, at 10:18, Jeff Mesnil <jmesnil@redhat.com> wrote:

Having said that, another Step that would be very interesting to showcase would be to run « mvn wildly:dev » make a tweak to the application codebase and see the changes in the running app.

This makes sense to me too. I'm not suggesting that we do this for the getting started, but I do think using run or dev makes sense there.


As an idea, I added a « step 4. Continuous Development » to my PoC at http://jmesnil.github.io/wildfly.org//getstarted/

That makes the experience a bit more playful and interactive.

jeff

--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/