You might want to read The Mythical Man Month for starters. On Jan 18, 11:39 am, Raphael André Bauer <[email protected]> wrote: > Hi, > > we are currently on the way creating the project infrastructure for a > larger GWT project. > The specs are: > - git > - Maven (using gwt-maven-plugin) > - around 100 developers > > My question is now: What are your recommendations setting up such a > large project and making teams productive? > > 1. I could think of one pom.xml with many gwt.xml modules. Cool: > Simple testing and debugging and deploying. > 2. But: Separating the gwt.xml modules into separate pom.xml is cool > as well. But there seem to be some drawbacks: Running and debugging > across the module boundary (developing on two modules at the same > time). But - of course the versioning is much nicer. > > Regarding 2) Should we use one git repository or one repository for each > module? > > I know there might be no definite answer on this. But I am sure there > are many people out that already have experience setting up larger GWT > projects. Can you recommend any best practices? > > Thanks! > > Cheers, > > Raphael
-- 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.
