Tutorial: webAppCreator deprecated but necessary for tutorials

[Reissner]

In https://www.gwtproject.org/gettingstarted-v2.html the tutorial states that webAppCreator is deprecated,
but the tutorials cannot be used without.
I think you cannot deprecate without providing an alternative.
The archetype gwt-maven-archetypes by Thomas Broyer
is no alternative for the tutorial.

GWT version: 2.11.0

Browser (with version): 123.0 (64-bit)
Operating System: suse tumbleweed

---

Description

In https://www.gwtproject.org/gettingstarted-v2.html the tutorial states that webAppCreator is deprecated,
but the tutorials cannot be used without.
I think you cannot deprecate without providing an alternative.
The archetype gwt-maven-archetypes by Thomas Broyer
is no alternative for the tutorial.

The tutorial refers to ant.
To reduce the gap, I would appreciate to read that webAppCreator can be used to create ant projects and maven projects.
For ant one may specify junit option, whereas for maven this does not make sense.
I would give ant only a mention and rework with the maven variant.

One can mention that the webAppCreator is from 2.11.0 on only for the tutorial.
It is advised to use the archetype of Thomas Broyer.

Maybe in webAppCreator one can make maven the default but ant is available still.
In a next step one can adapt webAppCreator to the new scheme.
Maybe it is sufficient just to provide a download link for the projects like stockwatcher, maybe a zip file.
But this makes sense only when abandoning ant altogether.

Steps to reproduce

Nothing to reproduce.

Links to further discussions

[Reissner]

I think the whole tutorial needs a rework transferring it from ant to maven.
If the webAppCreator is not adapted to maven, I find hard to figure out how to develop starting the right servers and so on.

I feel it is less effort and much more consistent to rework the webAppCreator so it uses Broyers archetype: this is what is already described how to work on and it is seamless.

[FrankHossfeld]

I feel it is less effort and much more consistent to rework the webAppCreator so it uses Broyers archetype: this is what is > already described how to work on and it is seamless.

Why adding more work on updating the webAppCreator instead of using the archetype directly? And which to use?
I know three archetype creators:

• gwt-maven-archetype (Thomas Broyer)
• gwt-maven-springboot-archetype (Disclaimer: I am the author)
• domino-cli

I total agree, the docs need updates. We are in the process of updating the docs and tutorials. But this is very time consuming job and take some time.

We appreciate any help from the community updating the docs and tutorial.