> Gotcha, thanks for the explanation. I worry that even if we can resolve all > the dependencies, you'll probably run into one of your dependencies relying > on some classes that GWT does not provide (for example, some of java.io). I > can't think of an easy way to avoid this except make your GWT code not rely > on Eclipse-provided plugins (only the server-side stuff depending on > Eclipse-provided plugins.)
... and that in turn means that I can forget using EMF, which is a deal-breaker. What a pity, I really liked the idea of the OSGi/ Eclipse plugin-architecture on the back end, while having a powerful web-gui-toolkit. Well, back to the drawing board. :-/ Cheers, - Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
