Experimental flags about gwt-gradle-plugin HOT 6 CLOSED

Sorry for the late answer. It seems I had some trouble with GitHub mail notifications.

I'll add the new flags introduced in GWT 2.7 soon. As a workaround, I guess this will work on a task level:

compileGwt {
    args '-someArg'
}
gwtDev {
    args '-someArg'
}

from gwt-gradle-plugin.

Thanks Steffen.

from gwt-gradle-plugin.

Hmm just for the record, I had to do the following:

gradle.taskGraph.whenReady { taskGraph ->
  if (taskGraph.hasTask(gwtSuperDev)) {
    gwtSuperDev {
      args '-launcherDir'
      args '/my/custom/launcher/dir'
    }
  } else {
    throw new RuntimeException("gwtSuperDev task not found.")
  }
}

If I don't do that Gradle complains that it can not find a method named gwtSuperDev() with argument .

from gwt-gradle-plugin.

@jnehlmeier this is because the gwtSuperDev task is added lazily depending on the configuration. So this task isn't available during configuration phase.
In addition to your example, there is another method to work around this:

tasks.withType(de.richsource.gradle.plugins.gwt.GwtSuperDev) {
      args '-launcherDir', '/my/custom/launcher/dir'
}

from gwt-gradle-plugin.

I added most (some special cases are missing) of the flags introduced in GWT 2.7.0-beta1.

GWT 2.7 introduces "-logLevel" for CodeServer (it already existed for the Compiler and DevMode). As this would break compatibility with older GWT versions, this flag isn't set by convention from the "gwt" extension. So currently, you have to set it manually for the task:

gwt {
    logLevel = "DEBUG"
}
tasks.withType(de.richsource.gradle.plugins.gwt.GwtSuperDev) {
    logLevel = gwt.logLevel
}

I'm evaluating a better solution for this and I hope I find a proper solution soon.

from gwt-gradle-plugin.

Closing because Steffens answer works for me.

from gwt-gradle-plugin.