ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <>
Subject Re: <script> needs a classpath param
Date Tue, 07 Aug 2001 07:08:26 GMT

>Okay, here's an idea.  There are a number of optional tasks that required
>support from external libs.  How about EXCLUDING these tasks by default,
>and requiring that they be explicitly declared in the build.xml, where a
>classpath can be provided.  For eg.
>    <taskdef name="junit" 
>             classname="">
><pathelement location="${optional.class.path}" />
><pathelement location="${junit.home}/junit.jar" />
></taskdef> Wouldn't that solve the problem?

It would if there were a third pathelement - the build/classes/ I have in mind.  It's good
but not
perfect as it forces all <script> or <junit> using targets to have the same classpath.

Regards - Paul H
CVS -1, Perforce +1

Do You Yahoo!?
Get your free address at
or your free address at

View raw message