Thanks for sending this. In the future, please submit patches like this as a
CVS diff as it makes our job a little easier. Also include the word [PATCH]
in the subject line as it will help us spot them.
In this case, there isn't an error, as the documentation for the method in
question states:
/**
* Test that the end method is called correctly when it's signature
* contains a <code>com.meterware.httpunit.WebResponse</code> parameter.
*
* Note: We need the Httpunit jar and an XML parser jar on the classpath
* for this test
*/
Note the second line.
Cheers,
Nick
-----Original Message-----
From: Jim Cheesman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 17, 2001 4:03 AM
To: [EMAIL PROTECTED]
Subject: Re: Building Cactus
Oops. Second question/problem - perhaps I should have waited a little
before the last question ;)
There's an error in the file org.apache.cactus.TestAbstractTestCase.java,
line 404. The line reads
public void endEndMethodOK2(com.meterware.httpunit.WebResponse theResponse)
It should read:
public void endEndMethodOK2(WebResponse theResponse)
(The file is found in
src\test\share\org\apache\cactus\TestAbstractTestCase.java, release version
1.2)
The corrected version is attached.
Jim
At 12:31 PM 17/10/01, you wrote:
>What's the reasoning behind defining the location of junit.jar and
>httpunit.jar in build.properties? From what I can see they are only used
>in defining the classpath element of the javadoc task in
>build-servletapi.xml - can't they be picked up from
%JAVA_HOME%/jre/lib/ext?
>
>
>(This question might be better asked on the ant list...)
>
>
>Jim
>
>
>
>--
>
> * Jim Cheesman *
> Trabajo: [EMAIL PROTECTED] - (34)(91) 724 9200 x 2360
> I am becoming increasingly worried that
> there isn't enough anxiety in my life.
