Is your classpath in your ant script (just ant, I think, on *nix, ant.bat on
Windows) getting screwed up?  And/or do you have your classpath configured
correctly?  Basically, you should check what classpath is getting passed
into the JVM that's starting up ant.  Depending on what platform you're on,
there are different ways to do this.  On Windows, just comment out all of
the "@echo off" statements in the scripts.  On *nix, just change the line
ant_exec_debug=false to ant_exec_debug=true and it'll echo out the command
before it runs it.  You can then look at the jars on the classpath and see
what you're getting for the Log class.

My guess is that the Jakarta Commons Logging library, Log4J, and Java
Logging libraries are getting mixed up somehow.  All of these have various
Log and Logger classes in different packages and I have had different
versions walk on each other and cause havoc.  The first thing to try is to
check that your classpath is clean and has only a single version of whatever
libs you need.

If the problem is actually occurring IN THE BUILD as opposed to just in the
ant run, then you need to check the classpath that's set up within the build
script itself.  That's totally dependent on the contents of the script.

Rick Herrick
[EMAIL PROTECTED]

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 11, 2006 3:50 AM
> To: [email protected]
> Subject: Log4JLogger does not implement Log
> 
> Hello,
> 
> I recently started encountering this classloading problem while running
> ant. According to the FAQ, I should post to this list so I can get some
> diagnostic tests to try. So... here I am! What tests should I try?
> 
> Nathan Meyers
> [EMAIL PROTECTED]
> 
> ---------------------------------------------------------------------
> 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