On Wed, Aug 9, 2023 at 9:31 AM Jeff Mesnil <jmesnil(a)redhat.com> wrote:
On 9 Aug 2023, at 18:25, James Perkins <jperkins(a)redhat.com> wrote:
On Wed, Aug 9, 2023 at 2:35 AM Jeff Mesnil <jmesnil(a)redhat.com> wrote:
> Hi,
>
> We are evaluating how we could improve the user experience for using
> WildFly and one of the idea is to create a « Get Started » page on
>
wildfly.org that would be an entry point for users that wants to try
> WildFly.
>
> This would be useful not only for new users (that have no previous
> knowledge of WildFly) but also existing users to let them understand the
> more recent ways to use WildFly.
>
> The expectation for this page would be simple:
>
> * no knowledge of WildFly required
> * Few prerequisites:
> * Java & Maven installed
> * Few steps:
> * Step 1: create a Maven project (using WildFly archetypes, more on
> that below)
> * Step 2: run mvn package
> * Step 3: run ./targer/server/bin/standalone.sh
>
Any reason not to combine steps 2 and 3 and suggest either using mvn
wildfly:run or mvn wildfly:dev?
>
I did not think about that :)
For this page, I wanted to have clear boundaries on the steps (this is how
you build, this is how you run).
Using a maven goal seems more in the direction we should move. The dev goal
will allow provisioning without having to run provision first. The run goal
will too, but it currently doesn't account for the provisioning settings.
We could easily change that though.
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.
--
Jeff Mesnil
Engineer @ Red Hat JBoss EAP
http://jmesnil.net/
--
James R. Perkins
JBoss by Red Hat