Hey, Isaac. That policy has proven very difficult to live with. (And to tell you the truth I forgot about it.)
The reasoning here was that we have released incubator jars that work with 1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it prove necessary to go back and do so we can go back and branch. In the meantime, we were faced bugs due to FastTree in particular being tied to the old StyleInjector while new development was moving to the version in GWT. We saw the opportunity to delete redundant code and took it. Is this going to cause problems for anyone? rjrjr On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett <itru...@gmail.com> wrote: > Last year, Emily stated that it would compile against the "latest > gwt-milestone and gwt-trunk". There hasn't been a 2.0 milestone that > I've seen, so under the policy from last year StyleInjector should not > have been removed in revisions 1712-1715. > > So, what's the current policy for incubator trunk compatibility? > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
