Thomas Broyer

If you don't mind, this will go into the release for GWT 2.6.0-rc2. Also, please squash all your commits together (unless it really makes sense to have several of them,...

Sounds good overall.

No short-term plan, no. Please experiment with the maven-assembly-plugin and report your experience here (should this be a ZIP? a JAR? how do you actually use it? etc.)

Or maybe you could _“just”_ configure the plugin with: ```xml ${project.build.directory}/${project.build.finalName} ``` instead of the `${project.build.directory}/gwt/deploy` default value: https://tbroyer.github.io/gwt-maven-plugin/compile-mojo.html#deploy

Do we really need an archetype for such a simple setup? → https://tbroyer.github.io/gwt-maven-plugin/usage.html Do you have something else in mind? (the archetypes here are about client/shared/server ; you'll note there's...

That's what I would do personally, yes. I could accept a PR but what would the archetype contain? only a pom.xml and module.gwt.xml? some Java code? what kind of code...

I've been a Linux user for years and I don't have any expertise on Windows idiosyncrasies. Patches welcome!

It might be due to an update of the plexus-utils dependency (from 3.0.16 to 3.1.0 between org.codehaus.mojo:gwt-maven-plugin 2.8.1 and 2.8.2; and from 3.0.21 to 3.1.0 in net.ltgt.gwt.maven:gwt-maven-plugin 1.0-rc-9 compared to...

Let's keep it open please. You have a workaround, but this still needs fixing (even if that only means waiting for a new version of plexus-utils with a fix and...

There is such a shutdown hook already, with the exception that it calls `destroy()` rather than `destroyForcibly()` (plexus-utils is likely to have/want to support old JVMs though, and `destroyForcibly()`w as...