I think pre-1.2, "init" was a special target that executed at start-up. If the documentation still suggests that's the case, then the doc should get updated (if you're so inclined, you can do that and submit a patch-file :)
I suppose you could consider adding another <project> attribute, similar to "default" (maybe "boot", or how about "onload" :) that would take the name of a target to always execute, even when other targets have been specified on the command-line (which "default" doesn't do). Diane --- James Bucanek <[EMAIL PROTECTED]> wrote: > So many questions... > > The documentation talks about "init" targets. On first reading, it > appeared that 'init' was a reserved target that would always get > executed first. > > I guess I was mistaken. It now appears that a so-called init target > is simply a target that all other targets depend on. Which means I > have to ensure that the correct 'depends' attribute is set for every > single target in my project or things won't work. :( > > So, is anyone contemplating defining a target, or a target attribute, > that causes a target to always get executed before any other > target(s)? > > Currently, my solution is to write some special code to automatically > add the 'init' target dependency to every other target before I start > the build. > > __________________________________ > James Bucanek > <mailto:[EMAIL PROTECTED]> > ===== ([EMAIL PROTECTED]) __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/
