ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Williams <mi...@cortexebusiness.com.au>
Subject Re: <script> needs a classpath param
Date Tue, 07 Aug 2001 22:35:39 GMT
  >>> On Tue, 7 Aug 2001 08:08:26 +0100 (BST),
  >>> "Paul" == Paul Hammant <paul_hammant@yahoo.com> wrote:

  Mike> <taskdef name="junit" 
  Mike>          classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
  Mike>     <classpath>
  Mike>         <pathelement location="${optional.class.path}" />
  Mike>         <pathelement location="${junit.home}/junit.jar" />
  Mike>     </classpath>
  Mike> </taskdef>

  Paul> It's good but not perfect as it forces all <script> or <junit>
  Paul> using targets to have the same classpath.

Er, I don't think so.  It only sets the classpath for defining the
JUnitTask; the JUnitTask class and supporting libs (ie. junit.jar).  

You can still specify a project-specific path to <junit> later on, eg.

    <junit>
        <classpath>
            <pathelement location="build/classes/" />
        </classpath>
        ...
    </junit>

-- 
Mike


Mime
View raw message