Incremental Build With Multiple GWT Modules about gwt-gradle-plugin HOT 3 OPEN

"if they have no dependencies between them" ... sounds like quite some work. The plugin would need to figure out the dependency tree of all supplied GWT modules.

I think you should just create an additional Gradle module instead so that you have a 1:1 mapping between compilable GWT module and Gradle module.

As a side note: The GWT Maven plugin of @tbroyer supports this 1:1 thought even more as it is able to generate the <inherits> of GWT modules based on the Maven module dependencies.

from gwt-gradle-plugin.

Maybe the plugin should instead create one compile task for each module?

That said, as a user, I think I'd be OK with the plugin not making such optimizations, and having to configure all the tasks (or just additional tasks) manually if I really want an optimized build.

from gwt-gradle-plugin.

Thanks for your answers. I have a couple of projects where I use GWT. If the project is pure GWT (one module) this is pretty much the setup to use. But in projects that utilize some parts GWT (multiple modules for different parts) rebuilding every single module, even tough only one was changed, can be the difference between a 2 minutes build time and a 15 minutes build time. This is handled somewhat OK when using an IDEA like IntelliJ but recently I've started migrating to a Gradle build.

from gwt-gradle-plugin.