If you fork <junit> then you can control the classpath more finely. Give that a try - it will probably do the trick.

Logging.... what a pain!

Erik


On Tuesday, August 12, 2003, at 02:49 PM, James Asher wrote:


I have a JUnit test that also uses HtmlUnit.

HtmlUnit is using commons-logging which in turn will
delegate to another logging framework.  If you are
using java 1.4 then it will use the java built in
logging support.  If you are not using 1.4 but have
log4j in your classpath then it will use that.
Otherwise it will use SimpleLog. How you change the
logging settings varies according to the logging
implementation you are using.

I am using Java 1.3, but I have log4j in my classpath.
 Is it possible to take out the log4j jar out of the
classpath just during testing and then put it back
after it?

Maybe somehow copy the current classpath to a
temporary classpath only used for unit tests and
remove the log4j jar then?

I dunno, just trying to figure out a solution.

Thanks.


__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to