Geek asks and answers

Gwt maven project flavors: WebAppCreator or gwt-maven-plugin-Archetype - what to use

I need maven project configuration for gwt project. The configuration should run in Eclipse (3.7 !?) and from the console (mvn, jenkins ...).

I tried webAppCreator with gwt:

webAppCreator.cmd -noant -maven -XnoEclipse -out WebAppCreated com.example.MyApp

And gwt-maven-plugin Archetype. Both projects look very similar in Eclipse, but they have very different configurations (different directories and using different plugins). I think that they will behave very differently if the project develops (adding tests, resources ...). Since the archetype configuration is much smaller, I would think that this is closer to the maven rules - but is this also better?

What are the effective differences between both configurations?

And what configuration would you suggest as a starting point?

+3
source share
1 answer

I always create POM from scratch, but if you ask me, I would choose the POM created by the artifact.

The POM created by WebAppCreator launches DevMode in target/www, which is strange, and includes a configurator maven-clean-pluginthat is simply not needed (you should never run DevMode using the src/main/webappdirectory as your war, so there is no need to clear it)

The POM generated by the artifact, on the other hand, uses targets i18nand generateAsyncwhich IMOs are not needed (they can be useful as tools for a single shot, but not run on each assembly, in particular i18n).

If you ask me, none of them will be a good starting point, but the artifact is less bad than WebAppCreator.

EDIT: : https://github.com/tbroyer/gwt-maven-archetypes , IMO gwt-maven-plugin WebAppCreator.

+6

More articles:


All Articles