Quoting Jim Carroll <[EMAIL PROTECTED]>: > On 4/4/07, Andrew Tomczak <[EMAIL PROTECTED]> wrote: > > I agree with Forest. It is typical of the Java development cycle. > > Two things that you can use to defend yourself from these problems are: > > 1) Have a full featured IDE like IDEA or Eclipse running (which can be just > as > > much of a pain in the but to setup and solve dependencies on a 64 bit > machine). > > This will quickly identify the missing libraries. > > 2) When a missing library is found, Google it. In fact Google is your > best > > friend when developing Java web applications. > > > > Yeah... I've been there. I'm using eclipse... but once I deploy my webapp > to > Tomcat, I get a missing dependency on log4j, but I've put log4j righth in > my > WEB-INF/lib directory.... it's one of those things where the problem must > be > somewhere else. > > Thanks, > -Jim >
I bet that there are two log4js. There is probably another one stashed away in Tomcat or the JRE someplace and it is conflicting with the one you added. If there are conflicting libraries neather of the two (or three) will work.
