Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by, but
I've also seen this trying to understand the general compiler changes that
are happening in trunk gwt - is the CompilerContext really an essential
part of ModuleDefLoader in general? From what I can see it is tracked as a
On Mon, Feb 10, 2014 at 2:57 PM, Colin Alworth niloc...@gmail.com wrote:
Just watched https://gwt-review.googlesource.com/#/c/6342/ wander by, but
I've also seen this trying to understand the general compiler changes that
are happening in trunk gwt - is the CompilerContext really an essential
Thanks for the reply - I'll keep watching ;).
W.R.T. designer, since existing installs are already broken and GWT 3+ is
going to again remove these deprecated methods, wouldn't it make more sense
to upgrade designer rather than downgrade ModuleDefLoader/DOM? (Keeping in
mind that I don't know
the ModuleDefLoader/DOM downgrade was in the GWT 2.6 release branch only
(since 2.6 is strictly expected to maintain compatibility).
The GWT 3.0 branch was not changed. GWT 3.0 is more open to backwards
incompatible changes and I agree/fully expect that for the 3.0 release the
right thing to do
