Hi Joerg, my situation is similar to what Thad is having. We are using code, that exists in projects that contain generic business logic functionality (used by different modules - not only gwt web ones), and among this functionality there are some utility classes that i need in GWT. I am searching a solution for avoiding code duplication.
I am not sure that the solution that you imply fits for the situation that I have. Regards, Marius. On Thursday, November 15, 2012 6:01:29 PM UTC+1, [email protected] wrote: > > Hi Marius, > > we are also doing maven and have a simple and consistent setup for GWT > projects: > > +myproject > | > +-+myproject-component1 > | | > | +-+myproject-component1-shared > | | > | +-+myproject-component1-client > | | > | +-+myproject-component1-server > | > ... > +-+myproject-componentN > | > +-+myproject-componentN-shared > | > +-+myproject-componentN-client > | > +-+myproject-componentN-server > > As far as I know this is the most common and suggested layout for a > modularized GWT application. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/61C66DQfeJ8J. 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.
