i'm only chiming in on the 3 letters RFC in the topic. the usecases being described as a point of deliberation, defining dependancies, repository access, and bundling automation, are well solved items in the maven stable. how hard can it be to define a multiproject descriptor, assign "channels" of build-stage progression, and have a top-level project build coordinated by one maven instance publish artifacts to sucessive build-channels served elsewhere by daemons which trigger maven sub-builds?
even if a GWT build is not in itself a maven project, there's very few reasons why a synthetic maven pom cannot be fashioned for a build-node graph to unify conventions of scm, artifact, versioning, and build hooks to prior documented art and tools. On Feb 10, 2010, at 8:12 AM, John Tamplin wrote: > On Wed, Feb 10, 2010 at 11:01 AM, James Northrup <northrup.ja...@gmail.com> > wrote: > there's a fairly large repository based elephant in the room named maven. > > I'm not sure what that has to do with sharding a compile of a GWT application > across a build farm. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
