On Wed, Feb 10, 2010 at 11:25 AM, James Northrup <northrup.ja...@gmail.com>wrote:
> 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? > That's a nice idea. Has anyone heard of a project using Maven to support distributed builds? The little bit of web searching I did turned up did not look good. People were saying it would be logical to build that way, but that Maven has a fundamental showstopper: the local repositories are not thread safe. Perhaps that has changed by now? Maven aside, there are other options. Hudson and Pulse should work well. Lex -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
