I'm not sure if it's a good practice.... To make this work in Eclipse, I had to create virtual src folders in each GWT application, the source of which was the source of the shared project.
Then there is a build.xml that copies source from all required projects into the build directory before launching the GWT compiler on it. The whole thing is then zipped up into the jar. On Mar 17, 10:43 pm, francescoNemesi <[email protected]> wrote: > Hi, > > I have a complex GWT application which is dependent on various other > GWT projects which are inherited. The application contains both server > and client code and it also uses external properties files. > > I would like to package this application into a jar which can then be > inherited by other projects. I am looking for references/best practice/ > case scenarios on how to do this in the best way possible, given the > complexity of the application. > > Any help/ideas welcome. > > Thanks, > Francesco -- 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.
