Mark, Not to quibble, but (IMHO) that's one of the main points of declarative systems. The developers declares the dependencies and the system is responsible to figuring out how to make it happen correctly. Sure, it's a little inside-out from a structural point of view, but it makes it easier to maintain large, complex systems because each node is as independent as it could be.
Just one developers opinion, - Paul Philion ----- Original Message ----- From: "Mark McMillan" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, December 18, 2001 9:53 AM Subject: Re: [Fwd: RE: Dependency analysis] > Oh, I missed the extra dependency you added. Yes, I think that would work, > although I don't like the way it will make the build file very fragmented > (for some one to figure out what ALL does, they have to find and examine > each dependency rather than just read what is inside the ALL target). I > prefer the clarity of the <do> task, but I see how it could be done just > using dependencies. > > -Mark > > At 09:25 AM 12/18/01, you wrote: > >On Tue, 2001-12-18 at 13:49, Mark McMillan wrote: > > > > > > >Can you not do something like: > > > > > > > ><target name="all" depends="init, compile, prep_work, borland, > > > >weblogic"/> > > > > > > Almost, but if the 'all' target needs to do some processing before the > > > 'borland' and 'weblogic' targets run, then it cannot do it. > > > > > > >I was allowing for the extra processing in the 'prep_work' target. Would > >that not work? > > > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
