On 06/01/2010, at 10:15 PM, Kristian Rosenvold wrote: > - Given that parallel execution is an "alternate" mode that may have > additional constraints, does 3.0 need something that is guaranteed to > work for the vast majority of projects ? I think Dan's implementation > does this already, while the Weave build would probably get there around > 3.1-3.2 if it is exposed as "experimental" through 3.0.
At a superficial level, this sounds like a great approach to me - a "safe" concurrent build by default, easily disabled for traditional style builds, with the infrastructure in place to make it much more and let people kick the tires. > The only significant difference between the weave mode and the regular > mode is that the complete execution plan is determined up-front. As a > consequence of this the ReactorArtifactRepository (line 83) is forced to > use compile output from upstream modules when in weave mode, which means > jar files from other modules are not used in weave mode. This is also > the reason for the problem with the Antrun plugin, I believe. I'll have > to go jogging (skiing), to come up with how to solve this. > > I'll look at the eclipse:eclipse issue ASAP. I may not fully grok this statement, but you certainly want all builds to utilise the same resources and behave the same way, no matter what mode they are operating in... Anyway, waiting for my flu to clear so I can dig into some of this in more detail :) - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
