> Jose Alberto Fernandez wrote: > > From: Siberski, Wolf [mailto:[EMAIL PROTECTED] [snip] > > E.g., we could have > > anttasks.jar all tasks needed to build ant > > -1, the definition cannot be "what is needed to build ANT". Is has to be > based on what is needed to build a reasonable application that does not > require some external or optional tool during the build process. > Using ANT as an approximation is one thing, but it cannot be the begining > and end. In particular, what do you mean by building ANT? just CORE or > the whole of ANT (optionals included)?
Just core. But why do You bother? If You want to build Ant, You'll download anttasks.jar. If You want to build EJBs, You'll download just ejbtasks.jar. If You want to build foos, You'll download footasks.jar. No Ant user would be forced to use the task collection designed for Ant developers. I'm sure we won't be able to agree about what "is needed to build a reasonable application...", so my goal is to avoid this discussion by providing several (overlapping) task collections which are targeted to different application types / Ant user types. Wolf
