At 02:47 29/3/01 +0100, Jose Alberto Fernandez wrote: >> Essentially it consists of possibly the following things >> * cross-buildfile dependencies >> * possibly cross-buildfile property access >> * sharing of "execution stack" (ie which tasks are already >> executed etc) >> * hierarchial scoping of properties (including const, overidable etc) >> * somethingelse???? > >I feel uneasy about some of these, in the general case. As someone said, >this may allow for spagetti code like builds. However, there is a particular >subset where I think it may be granted: <antcall>.
antcall is not sufficient - cross project dependencies need to be part of dependency graph essentially. While this could be done by hacking at antcall it would not be easy/intuitive. scoping is necessary even now Thus I assume the two you are uneasy about are 1. possibly cross-buildfile property access 2. sharing of "execution stack" (ie which tasks are already executed etc) (2) is only necessary if we allow cross-project dependencies or sequential ordering of dependencies. (1) could be scary though ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*
