> Or should I go ahead and propose a patch that deprecates it or even > removes it?
That seems like a great idea to me; I would say go ahead and submit a patch to remove it. I suppose it is inevitable that some internal Google projects still use it, but it would be nice to at least know, and I think Ray/Brian submitting a patch and letting their build system figure it out what breaks is the quickest way to know. If anything we can queue it up for the eventual non-google trunk where hopefully we have a bit more freedom with this sort of stuff. - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
