Chenge the behavior of the gwtDev task about gwt-gradle-plugin HOT 6 OPEN

I hope I understood the problem right ....
When starting gwtDev, the dev mode window will appear at some time. If I remember right, the gradle process terminates if you close that window. That should also be the case if a debugger is attached to this process.

It is intended behavior that the gradle process runs while gwtDev runs. This makes it possible to log to the attaches console. If a background process would be spawned it would either cause another console window to open or the log would be lost.

What would be helpfull in my point of view is the possibility to kill running gradle tasks out of the IDE. But unfortunately there's a bug in Gradle that prevents IDE developers to do that: http://issues.gradle.org/browse/GRADLE-1539

from gwt-gradle-plugin.

Let me try to explain again:

1. there is no need to keep the gradle process running once you launched dev mode. This results in memory waste only.
2. gwt dev has its own console where all errors/exception show (this is one of the tabs of the UI) , so none of the log messages would be lost and there is no need to keep the gradle console for that.
3. It is very easy to kill the gwt dev process without the parent gradle process - just click on the [X] control of the gwt dev window and it dies immediately.

My point is that there is really no need to keep the parent gradle process once you launched gwt dev.

from gwt-gradle-plugin.

Only Client only log messages (GWT.log/TreeLoggerStuff) are shown in the DevMode window (yes I know where to find it). The important part here is server side logging. These logs would get lost if changing the behavior this way.

If I remember right, client side logging via java.util.logging will also not be shown in the DevMode window. If using remote logging you would expect to see those log messages in the console window or Eclipse.

As the gwt-maven-plugin implements the exact same behavior I would also treat it as default behavior.

from gwt-gradle-plugin.

What if one does not use the built-in jetty server at all? Perhaps the best
way isbtoballow the user to either spawn or not gwtdev...
On Dec 4, 2013 3:04 AM, "steffenschaefer" [email protected] wrote:

Only Client only log messages (GWT.log/TreeLoggerStuff) are shown in the
DevMode window (yes I know where to find it). The important part here is
server side logging. These logs would get lost if changing the behavior
this way.

If I remember right, client side logging via java.util.logging will also
not be shown in the DevMode window. If using remote logging you would
expect to see those log messages in the console window or Eclipse.

As the gwt-maven-plugin implements the exact same behavior I would also
treat it as default behavior.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-29796212
.

from gwt-gradle-plugin.

For the record -> This is related to http://issues.gradle.org/browse/GRADLE-1254

from gwt-gradle-plugin.

I know and I asked the gradle team when this be fixed. In the meantime, the
workaround is to use Ant's exec task as I showed you with the snippet of
Gragle/ant code. Ant's exec can spawn and works well and all Ant tasks are
automatically available in Cradle.
On Dec 4, 2013 12:05 PM, "steffenschaefer" [email protected] wrote:

For the record -> This is related to
http://issues.gradle.org/browse/GRADLE-1254

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-29840038
.

from gwt-gradle-plugin.