Mark,
Things should much smoother with the recent updates. In case of missing jakarta-oro.jar or junit.jar files, the new failures messages should also help the user figure out the corrective steps.
At 07:10 AM 12/9/2004, Mark Womack wrote:
I had a heck of a time with the test cases. First it was complaining that it could not find a ./test/lib directory. Then it was complaining that it could not find jetty related classes. Then it was complaining about the test cases being invalid with JUnit.
AGH! I know I have been out of it for a while, but wow!
So, I updated the README to explicitly document the ./test/lib directory (good idea, btw) and what jars will be needed. Someone should review it. I think that JUnit 3.8 is now required because I could not get test cases to compile using 3.7. I also got rid of the jakarta.oro.jar property in favor of having it in the ./test/lib. That might break GUMP, I don't know.
I still get errors related to the joran test cases, but I don't think these are related to the above changes. But maybe not.
BUILD FAILED
D:\development\code-cvs-jakarta-projects\logging-log4j\tests\build.xml:515: Test org.apache.joran.InterpreterTest failed
-Mark
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
