Nico Seessle wrote:
>
> ----- Original Message -----
> From: "David Corbin" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, December 24, 2000 2:32 AM
> Subject: Re: Setting classpath
>
> > And, I've discovered, when you set the classpath for the junit task, you
> > have to add both optional.jar and ant.jar to the classpath (at least you
> > do if you have "fork" set).
>
> What are you testing? And what is Ant's reaction if you don't include these
> two jar's in the classpath? (ClassNotFoundException? With what class?)
Yes. ClassNotFoundExceptions.
org/apache/tools/ant/taskdefs/optional/junit/JUnitTestRunner
When I re-checked, I found that I was wrong about ant.jar. optional.jar
and (of course) junit.jar are necessary. But it seems these are both
necessary to define the taskdef (as I recall, though my memory hasn't
been great lately), they ought to be included automatically.
>
> > Is there anyway to refer to the classpath that ant's VM was invoked
> > with?
> You can refer to it using java-properties, but I don't think you can use
> this to set up a classpath (but I have not tried it :-) )
>
How does one refer to java-properties? Is that the same as other "ant"
properties, explicitly defined in the build.xml.
> Nico
--
David Corbin
Mach Turtle Technologies, Inc.
http://www.machturtle.com
[EMAIL PROTECTED]
