gwt + eclipse plugin about gwt-gradle-plugin HOT 4 CLOSED

Actually, the problem was that the GWT plugin uses the directory "war" during the build process, and we also happened to have this as our actual webAppDir.

There should throw a warning / error in this case, as these are in conflict.

from gwt-gradle-plugin.

The gwt-gradle-plugin is made to work with the eclipse plugin. But GWT, especially the Google plugin for Eclipse has different philosophy than what you expect if building Java web applications using Maven or Gradle. Let me explain that a little bit:
Gradle typically uses Maven's standard project layout where the static web application resources are located under src/main/webapp. Gradle/Maven would never write to this source directory.
Google plugin for Eclipse uses the folder "war" for the web application resources. In addition it writes GWT compiler outputs/jars/classes and other stuff to this directory. So you get a mix of source files and compiler output. This is a no-go in the Maven/Gradle world. But this additional stuff is needed to make e.g. GWT dev mode work in Eclipse.

The gwt-gradle-plugin tries to work around this by assuming that you have a web application source directory (e.g. src/main/webapp) and a working directory (e.g. war). The first will be the source directory you typically commit to version control. The second one is generated by copying the wb application sources + the libs so that GWT dev mode will work in Eclipse by using this directory (this is done by warTemplate task).

If you configure both directories to be the same (and I guess you did that), you will get a crazy behavior because the working directory is cleaned before it is created from the web application sources.

I hope that helps.

from gwt-gradle-plugin.

Oh, just recognized you answered this by yourselves while I wrote my answer.
Yes, you are totally right, there should be a warning about this.

from gwt-gradle-plugin.

Thanks for the detailed and quick response!

from gwt-gradle-plugin.