On Wed, Jan 13, 2010 at 9:46 PM, Kevin Daly <ked...@sqm.ca> wrote: > It's now compiling for me. The errors don't seem to cause any issues. I guess > it will all be worked out in the next milestone. > > see this post in the bug tracker. > > http://restlet.tigris.org/issues/show_bug.cgi?id=1004
Not sure if we are observing the same problem. I have all the while had the GWT served from one webapp (.war) and the Restlet based server in a different webapp. All the while the GWT edition of org.restlet (and servlet) has been separated from the JEE edition during compile, so I don't think it is related. (Or do I misunderstand your explaination?) I have worked off the HEAD for a while, but can't pinpoint the time of breakage, whether it was something that changed in Restlet, my introduction of GWT 2.0 OR some statement that I have added that triggers the problem. After all, doesn't GWT only traverse the usage graphs of classes when it decides what to be pulled in? I'll see if I can pull together a really tiny testcase... Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2437053
