Thanks for the comments on various build systems. I have been scanning all of their docs. The strange thing I am noticing is that while they all allow concurrency, it generally seems to be a after thought for multiple projects. The buck facebook comment says 2x faster, however I am thinking a well organized build with massive concurrency would be a much faster. For example if the concurrency unit were the project, and it had to do the following for four projects A,B,C and D.
git compile/jar test If B, C and D depend on A, massive concurrently this would look like. git A B C D (4x faster) compile/jar A (same) compile/jar B C D, compile/jar C (3x faster) test A B C D (4x faster) If the single threaded approach took 12 minutes (1 minute for each step) the massive concurrent approach would take 4 minutes or 3x faster. If your had a X_tests project for each other project it would enforce a well optimized build. I am thinking of wrapping the java part of ant and maven in java to accomplish this, but it would be a huge time commitment/amount of work. Although it would be backward compatible with anything ant can do now :)_ Cheers, Scott -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/fa0e9803-2368-465a-b897-e2bf6780f7d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
