On Jan 14, 2008 5:39 PM, Dominique Devienne <[EMAIL PROTECTED]> wrote: > On 1/14/08, Peter Reilly <[EMAIL PROTECTED]> wrote: > > On Jan 14, 2008 5:02 PM, Wolfgang Häfelinger <[EMAIL PROTECTED]> wrote: > > > 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. > > > > 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>.
Opps, I just read the previous e-mails, and yes you have proposed this syntax!. > > 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? > > 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? This is the <target override="build"> syntax? I am a little dubious, but could be swayed. Peter > > Both questions above are independent of using overriding macros... --DD > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
