> Peter is +1 on allowing tasks outside of targets but -1 on allowing a > build file without targets.
- A build without any targets is a bad practice, isn't it? So why bother making it possible? - Consistency is a good thing. All tasks executable outside of a target is consistent. But wait a minute! AFAIK many or all of the outside-of-a-target-executable tasks are only setting up data types, initializing paths/taskdef and stuff like those. They are not really tasks, but initializers. Maybe define a new interface and let Initializer tasks be placed outside of a target? The documentation can show it clearly with an icon, or maybe move all these initializer tasks to a separate section? Ara. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
