You only need to gwt compile once, then just run DevMode.
Ideally, you'd point DevMode's -war at the location Jetty loads your webapp
(so, deploy an exploded WAR, or point -war to the location Jetty exploded
the WAR in the temp folder) so that all the static files it generates
What you're describing is pretty much what we're doing.
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't stop, recompile from the command line
(including gwt compile) the updated DTO can't be sent/received...the
GWT-RPC stuff doesn't
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't stop, recompile from the command line
(including gwt compile) the updated DTO can't be sent/received...the
GWT-RPC stuff doesn't match up any more and we get failures.
You just
It looks like Opera 12's market share (the last non-webkit Opera version)
is now below 0.5% and newer versions already should use the webkit
permutation. The support was already very weak and we don't see any reason
to continue it.
Similar to IE6/7 deprecation, we will start with disabling the
Just to confirm, the plan is to set this in master as well as releases/2.6,
and this will go out in 2.6.0-rc2?
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe
Yes, that's correct.
On Wed, Nov 20, 2013 at 12:08 PM, Colin Alworth niloc...@gmail.com wrote:
Just to confirm, the plan is to set this in master as well as
releases/2.6, and this will go out in 2.6.0-rc2?
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received
Yes, that's correct.
Should be fine.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
