My response was incomplete. I found a classpath entry which was referencing 1.1.4. I changed that reference to point to the current version as well. My bad.
> -----Original Message----- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 04, 2002 9:40 AM > To: Log4J Users List > Subject: RE: Unexpected Exception launching through Ant > > > > I beg to differ. You probably recompiled in the upgrade process. If > you go back to 1.2.5 the problem will still be "solved". The > difference between 1.2.6 and 1.2.5 cannot cause a > java.lang.VerifyError exception. At least not in a rational world. > > Nevertheless, thanks for reporting back. > > At 09:14 04.09.2002 -0600, you wrote: > >I upgraded from 1.2.5 to 1.2.6 and the problem resolved itself. > > > > > -----Original Message----- > > > From: John Muhlestein [mailto:[EMAIL PROTECTED]] > > > Sent: Tuesday, September 03, 2002 4:48 PM > > > To: '[EMAIL PROTECTED]' > > > Subject: Unexpected Exception launching through Ant > > > > > > > > > I am attempting to launch an application using Ant that I > > > just added logging > > > to and I am getting an unexpected error. > > > > > > Buildfile: build.xml > > > > > > launchGUI: > > > [java] java.lang.VerifyError: (class: > > > org/apache/log4j/LogManager, method: <clinit> signature: ()V) > > > Incompatible > > > argument to function > > > [java] at > > > org.apache.log4j.Logger.getLogger(Logger.java:85) > > > [java] at > > > com.ilink.noc.routemanager.gui.MainAppFrame.<clinit>(MainAppFr > > > ame.java:28) > > > [java] Exception in thread "main" > > > > > > BUILD SUCCESSFUL > > > Total time: 3 seconds > > > > > > Here is a snippet of the code to instantiate the Logger > > > (which is line 28 > > > from the above error) > > > static Logger logger = > > > Logger.getLogger("com.ilink.noc.routemanager.gui.MainAppFrame"); > > > > > > And the <target> info from my build.xml > > > > > > <target name="launchGUI"> > > > <java classname="com.ilink.noc.routemanager.gui.MainAppFrame" > > > fork="yes"> > > > <classpath> > > > <pathelement path="${env.CLASSPATH}" /> > > > <pathelement location="${JavaClasses}" /> > > > <pathelement location="${JavaLib}/xercelImpl.jar" /> > > > <pathelement location="${JavaLib}/xmlParserAPIs.jar" /> > > > <pathelement location="${JavaLib}/oraclejdbc.jar" /> > > > <pathelement location="${JavaLib}/log4j-1.2.5.jar" /> > > > </classpath> > > > </java> > > > </target> > > > > > > > > > Has anyone encountered this before or have any ideas? > > > > > > thanks, > > > John > > -- > Ceki > > TCP implementations will follow a general principle of robustness: be > conservative in what you do, be liberal in what you accept from > others. -- Jon Postel, RFC 793 > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
