Eric is right... even though I've only authored one book (working on the second right now... errr, *should* be working on it right now!) I know what he's talking about... with regard to GWT specifically, the simple answer is that it wasn't announced (at least, I wasn't aware of it having been announced) while I was writing the book... by the time it was announced, the book was almost complete and it would have been too late to change it to include GWT.
On a side note, I'm not so sure you would have WANTED me to cover it
To me, it's a wonderful piece of technology, as a developer I'm quite impressed by it, but in terms of evaluating for use in my organization, my opinion is less enthusiastic, to put it nicely
and I can't imagine ever recommending it. YMMV.
Although, one thing I've learned about the publishing business very quickly is that while you can certainly sneak your opinions in here and there (I think readers WANT you to in fact), it's all about marketing, and if a lot of people wanted to read about GWT, my editor would be pushing me to include it, and I'd be stupid to fight him on that! (my current book isn't slated to use it, but I'm early enough in the process that it could get added... haven't really considered it, but I just may now)
-- <br />Frank W. Zammetti<br />Founder and Chief Software Architect<br />Omnytex Technologies<br /><a href="http://www.omnytex.com" target="_blank" rel="nofollow">http://www.omnytex.com</a><br />AIM/Yahoo: fzammetti<br />MSN: fzammetti@hotmail.com<br />Author of "Practical Ajax Projects With Java Technology"<br /> (2006, Apress, ISBN 1-59059-695-1)<br />and "JavaScript, DOM Scripting and Ajax Projects"<br /> (2007, Apress, ISBN 1-59059-816-4)<br />Java Web Parts - <a href="http://javawebparts.sourceforge.net" target="_blank" rel="nofollow">http://javawebparts.sourceforge.net</a><br /> Supplying the wheel, so you don't have to reinvent it!