Yes, that explains it, but that doesn't mean it's good. This whole business of having the top-level tasks execute when you run -projecthelp or an error message about a missing target being issued after top-level tasks execution is not a good thing.
It's unexpected, and feels wrong. I don't have a good alternative that would be backward compatible, but this is yet another wrinkle or gotcha of Ant. I've always felt authorizing any top-level tasks brought little to Ant in terms of usability, and had mostly downsides. Oh well, another lost battle ;-) --DD > -----Original Message----- > From: Jacob Kjome [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 05, 2004 11:40 AM > To: Ant Users List > Subject: Re: running tasks without a target actually works? > > Ahhh... Ok, that explains it exactly. Thanks Peter! > > Quoting Peter Reilly <[EMAIL PROTECTED]>: > > Since ant 1.6.0, tasks can live outside targets. > > These tasks always get run before target resolution - hence > > your error line. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
