I already place all my setup stuff in an "init" task that requires that the public-target task have been run to set a property... preventing command line invocation of targets that don't depend on both init and public. (or neither, but all tasks in my files depend on "init"). Such a change would quite definately break my builds.
-Gus Stefan Bodewig wrote: > > On Thu, 18 Jul 2002, Stephane Bailliez <[EMAIL PROTECTED]> wrote: > > but don't you think it would be better to have some sort of reserved > > keyword for a target like "init" or whatever that will be always be > > invoked at runtime before anything ? > > And break old build files because you couldn't place <property> > outside of targets. > > No magic names, please. A new construct like <init> has been > discussed and vetoed before. > > Stefan > > -- > 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]>
