--- Stefan Bodewig <[EMAIL PROTECTED]> wrote: > (1) You still need at least one target for Ant to do something. > > I'd like to drop this limitation, which at the same time means we'd > have to make the default attribute of <project> optional - leaving it > out would mean that only the tasks that are not part of any target > would be run.
+1 I'm assuming everything outside of any target will always get run, whether there's a default or a command-line target given (unless you're just getting projecthelp.) > (2) If we change (1) we need to revisit <ant> and <antcall>. > > Currently <ant> and <antcall> without using the target attribute > implies running the called project's default target. What if there is > none? Run the tasks that are not inside targets? That's what I'd expect it to do. > (3) ant -projecthelp will run the tasks that are outside of targets. > > It has been doing so for <property> and <taskdef> since it has been > invented, but nobody has noticed. Now this will become a problem. > > I think we'll have to change ProjectHelper's interface to tell > ProjectHelper to only parse but not run tasks. Sounds reasonable to me. Diane ===== ([EMAIL PROTECTED]) __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
