Comments (6)
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:
- there is no need to keep the gradle process running once you launched dev mode. This results in memory waste only.
- 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.
- 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.
Related Issues (20)
- [gwt 2.7.0/gradle 2.12./plug-in 0.6] gwtSuperDev - java.lang.OutOfMemoryError HOT 8
- [GWT 2.8/Pluging 0.6] Issue with gwt sub-projects HOT 1
- [GWT 2.8-SNAPSHOT/Gradle 2.13] Properties issue HOT 5
- Make gwt-unitcache and war directories configurable
- gwt + gradle + lombok issues resolved
- Have any way to generate i18n and generateAsync supported by gwt-maven-plugin? HOT 6
- vaadinCompile issue, with vaadin 8 at 1.0 version
- compileGwt is missing module descriptor of a submodule on classpath HOT 8
- Make the compile tasks cacheable
- Missing support for Gradle Composite Builds
- Gradle ... single directory for all classes .. is scheduled to be removed in Gradle 5.0 HOT 1
- gwt-gradle-plugin uses deprecated api by Gradle 4.0 HOT 3
- Updated GPE Changes Property Variables
- GenerateGdt Task Needs To Also Be a Dependency of eclipseWtp
- Gradle upgrade to 5.4 causes build failure HOT 3
- CreateProcess error=206, The filename or extension is too long HOT 1
- Buildship Support HOT 1
- Has this plug-in been tested with GWT 2.8.Beta? HOT 2
- Integreation with Gretty plugin
- example build failed HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gwt-gradle-plugin.