We now have a very "standard" set of apps with all sorts of modern features, which we expected our users to take advantage of, but there is still room for additional improvements, thus we have the following CY2024Q3 Quickstarts Enhancements in my mind:

• Prioritising server provisioning

Up till now our priority has been the standard distribution, but server provisioning introduces many advantages, such as the fact that a trimmed server is more secure and performant, and the fact it's easier to migrate config change scripts than a whole xml config, and I believe it's now the time for quickstarts to prioritise server provisioning. Please note that doesn't mean to only change order of README instructions, when server provisioning is applicable we should always build both the standalone deployment (for bare metal), and the provisioned server. From my experiments we lose about 7 seconds by doing this, yet we improve user experience (less instructions, no need to use profiles, etc.) and it allows us to use high level modern WildFly Maven Plugin goals "anytime".

• No deployment at web root

When switching from traditional server distribution, to bare metal server provisioning or OpenShift, today we deploy quickstarts at the web root, and while this feature makes sense to showcase (it's a single deployment app server) it also introduces complications wrt usage instructions that affects the overall user experience (URL changes, CLI param changes, etc.). We should now change this and use the standard deploy strategy for all supported environments.

• Usage of modern multi-action WildFly Maven Plugin goals

The Wildfly Maven Plugin has evolved and provides high level goals which do multi-actions, such as wildfly:run (equivalent to "old" build, package, deploy, start) and wildfly:dev (equivalent to "old" build, package, deploy, start with live coding), which we should take advantage to minimize number of cli commands and showcase modern app development.

• JUnit 5

Midway of previous enhancements some people start asking to use JUnit 5 instead, and while we don't make any usage of any new features it's now time to apply this move to all quickstarts.