> > > > Assume also: > > > > > > > > <target name="prepare" before="junit"> > > > > <prepare /> > > > > </target> > > > > > > > > Do you want this before your "start-server" or after it or > > > > in parallel? > > > > > > > > > > I would say that if the build file does not specify the order, > > > then the order is undefined.
maybe document order and import tree can be used to define that order? > > > If the order is important, then the build file can enforce an order by > > > using "depends". > > > > > > <target name="prepare" before="junit" depends="start-server"> > > > <prepare /> > > > </target> > > > > It makes sense Peter. And this already works in Ant, provided we add > > before/after support to <target>. > > > > Q1: Does everyone agree that adding before/after to target to Ant 1.8 > > is useful and should be done before (in conjunction of) creating > > generic build files? > > I agree, this seems easily understandable (even though when used in > conjunction with depends it may seem a bit complex, but this shouldn't > be needed very often) and use the usual Ant building blocks. > > > > > > > Q2: Do others feel (like me) that we should also have a mean to > > override a target's content (task list) while keeping the overridden > > target's dependency list? > > I do. And also add the <super /> element you were talking about. > > Xavier a) override="both" b) override="content" c) warn otherwise! Guntis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
