Wednesday, April 26, 2017

Re: Why incremental compiler option defaults to OFF?

I have no problems running the gradle tasks. The main problem is a lot of manual work in the process of debugging the code.

gwtDev ->debug code->gwtStop->gwtRun->debug code->gwtStop->gwtRun->debug code->gwtStop->gwtRun->....->edit librirary code->Gradle refresh->gwtStop->gwtRun -> 

среда, 26 апреля 2017 г., 20:14:55 UTC+4 пользователь Gordan Krešić написал:
Works for me™ :)

I did have troubles setting up everything for the first time, but I'm still not very fluent with Gradle, so can not say how much those troubles were related to Putnami and how much to Gradle itself.

Right now, most of my build-related troubles are related to Buildship (Eclipse Gradle plugin) and not that much to Gradle (and Putnami). If you have troubles running Putnami tasks from Eclipse, try running them from command line, just to rule out Eclipse/Buildship as source of your pains.

On Wednesday, April 26, 2017 at 5:47:16 PM UTC+2, Олег Рачаев wrote:
I ask you offtop questin: how far you progress with putnami gradle plugin. I've managed to setup and work with it. But I realize more and more that gwt+gradle+putnami=pain. Sometimes i feel soo tired so I want go back to vanilla gwt+ant+eclipse plugin

четверг, 1 декабря 2016 г., 13:01:27 UTC+4 пользователь Gordan Krešić написал:
When turned ON, -incremental should "compile faster by reusing data from the previous compile". Why it is not turned on by default? Are there any caveats?

Google gives me mostly SDM related use-cases which I understand. But I'm wondering if using incremental compilation may speed up regular Gradle builds. If it matters, I'm using Putnami Gradle plugin.

You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
For more options, visit

No comments:

Post a Comment