AB, You could go that way. Cobbling together a module using a script will defeat some of your IDE features, though, depending on what IDE you use.
GWT Modules are transparent and non-intrusive to javac compiling, so you should be able to accomplish what you need with a small number (one?) of gwt.xml files strategically placed in your existing hierarchy. If I were you, I would probably refactor for GWT/Java reuse, though. Take your util files, put them together somewhere in GWT module arrangement, include that location on the javac classpath if not already there, and inherit the module wherever your GWT code needs util services. It's not necessary for every Module to have an entrypoint. It's necessary that the transitive closure of inherited modules for a given compile have an entrypoint. Hope this helps, Walden On Nov 4, 3:13 pm, AB <[EMAIL PROTECTED]> wrote: > Thanks all. I guess Ill create an ant task that cobbles together > various util classes that we want and build a module. I dont know if > I need to fabricate an entrypoint for this module but i guess I can if > the compiler demands it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
