You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Mark Womack <mw...@apache.org> on 2004/12/09 07:10:32 UTC
Test Update
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
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Test Update
Posted by Ceki Gülcü <ce...@qos.ch>.
At 07:49 PM 12/9/2004, Mark Womack wrote:
>Ceki,
>
>Thanks.
>
>Actually I should have said that I got rid of the " jakarta.oro.jar
>property" instead of the jar. I noticed that you added the property back.
>But, with the lib dir, we don't seed to have individual properties anymore.
Put it back for the sake of gump. If you want, you can put
jakarta-oro.jar in tests/lib and it'll work.
Note that for those with an existing build.properties file, I changed
the name of the property to "jakarta-oro.jar" from "jakarta.oro.jar".
The change is a little hard to spot.
>I view that as a good thing. Just document as needed in the README and
>update the new prerequisites task you added to check for required jars.
The checks are already there.
>-Mark
--
Ceki Gülcü
The complete log4j manual: http://qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Test Update
Posted by Mark Womack <wo...@adobe.com>.
Ceki,
Thanks.
Actually I should have said that I got rid of the " jakarta.oro.jar
property" instead of the jar. I noticed that you added the property back.
But, with the lib dir, we don't seed to have individual properties anymore.
I view that as a good thing. Just document as needed in the README and
update the new prerequisites task you added to check for required jars. We
should look at doing that in the main build file too, IMO.
-Mark
-----Original Message-----
From: Ceki Gülcü [mailto:ceki@qos.ch]
Sent: Thursday, December 09, 2004 7:16 AM
To: Log4J Developers List
Subject: Re: Test Update
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Test Update
Posted by Ceki Gülcü <ce...@qos.ch>.
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org