On Mon, 31 Jan 2005, Douglas Kramer <[EMAIL PROTECTED]> wrote: > Stefan Bodewig wrote:
>> PropertyFile doesn't need any additional library. > > Then why is it an Optional task? Because we once decided to call it an optional task. > What's optional about it? Did it used to be optional? There may have been a JDK 1.2 dependency when Ant was supposed to work on JDK 1.1, I'm not sure. > In fact, the following paragraph refers to core tasks as "built-in", > implying that optional tasks are not built-in: > > There is a set of <a href="coretasklist">built-in tasks</a>, > along with a number of <a href="optionaltasklist">optional > tasks</a>, but it is also very easy to write your own. It's pretty much along the lines of Peter's answer, built-in = "part of ant.jar" > If it was optional for some earlier version of Ant but is > no longer optional, please document at which version it > became core. Really, there is no clear distinction between core and optional. Much of it is historic. >>>But the documentation doesn't seem to mention clearly which >>>libraries they reside in. >> The tasks reside in the Ant download, you need the library to run >> the tasks. > > I don't understand this. I need which library to run the tasks? Maybe it gets easier if we use a concrete example, <junit>. The junit task is in ant-junit.jar, which is part of the Ant 1.6.2 binary release bundles. To run the task, you need JUnit itself in addition to the task. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
