On Friday, May 11, 2012 4:12:16 PM UTC+2, Ümit Seren wrote: > > Thanks for the feedback Thomas, > I was actually following the gwt_with_maven docs at the google developers > page (tough only creating one maven war project). > So I think it should be quite easy to split it up. >
Yes, very easy (provided you understand what you do and what you *need* to do). > BTW. do these 3 (or 4 respectively) modules go into separate VCS > repositories or do all go into one? > I guess they could be checked into separate VCS repositories as the > dependency is handled by maven anyways. > These are all Maven modules under a "super-module", so we use a single VCS repo. It depends on your modules' lifecycle management; we always release the whole "package", so it makes no sense to have them as separate modules tracked independently (in independent VCS repos, with independently evolving version numbers, etc.) > How do you do deployment? Do you have a dedicated jetty instance on the > production server and package the war and deploy it? > We have a quite specific setup, where we have a dedicated Jetty instance that's quite heavily tuned and adapted to our needs (many objects –including an HornetQ event-bus– instantiated in Jetty's XML files, and some of them passed to our app via JNDI). Our deliverable includes the Jetty configuration and startup scripts, WARs (we have several apps, only one using GWT) and shared libs. For other projects with no/less specific needs, packaging as a WAR and deploying in whatever servlet container (or even EAR / application server) would Just Work™. In Maven, you could use Cargo <http://cargo.codehaus.org/> instead of jetty:start if you wanted. -- 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/-/dtdrHubAQcIJ. 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.
