Most of these don't really apply to GWTShell either -- they should be
on
Compiler (etc) and JUnitShell (since it can run the compiler for
web-mode
tests).
New patch uploaded that moves all of the compiler-eqsue flags over to
JUnitShell.
http://gwt-code-reviews.appspot.com/92804
LGTM assuming ant test still works.
http://gwt-code-reviews.appspot.com/92804
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
Are we never going to re-enable compilation from the Swing UI?
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
On Wed, Nov 4, 2009 at 11:18 AM, Scott Blum sco...@google.com wrote:
Are we never going to re-enable compilation from the Swing UI?
I didn't think that was on the table for 2.0, so in the interest of
minimizing confusion, the options should be removed.
--
Bob Vawter
Google Web Toolkit Team
On Wed, Nov 4, 2009 at 12:18 PM, Scott Blum sco...@google.com wrote:
Are we never going to re-enable compilation from the Swing UI?
Not in 2.0, and even then it would probably be better to expose those
options graphically rather than requiring them to restart DevMode if they
want to change to
Sold.
On Wed, Nov 4, 2009 at 11:27 AM, John Tamplin j...@google.com wrote:
On Wed, Nov 4, 2009 at 12:18 PM, Scott Blum sco...@google.com wrote:
Are we never going to re-enable compilation from the Swing UI?
Not in 2.0, and even then it would probably be better to expose those
options
