I suspect this will be to do with overlapping classpaths between ant (the system classloader) and the classloader being used within the JUnit task. For me, I had problems only under hotspot, which seems to have a slightly different way of managing loaded classes. Under 1.3 without hotspot, it would be OK.
I wrote down some info when I was working on the class loader for EJBC which I can provide, if I can find it. I have had reports of some people having similar problems with ejbc lately although I haven't had time to follow those up in detail yet. Conor +1 on classloaders being a pain. -- Conor MacNeill [EMAIL PROTECTED] Cortex eBusiness http://www.cortexebusiness.com.au > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 10 October 2000 2:59 > To: [EMAIL PROTECTED] > Subject: Re: Build Failed > > > Stefan Bodewig wrote: > > > >>>>> "EM" == Erik Meade <[EMAIL PROTECTED]> writes: > > > > >> From: Stefan Bodewig > > > > >> Which JDK is this? > > EM> C:\>java -version java version "1.3.0" Java(TM) 2 Runtime > > EM> Environment, Standard Edition (build 1.3.0-C) Java HotSpot(TM) > > EM> Client VM (build 1.3.0-C, mixed mode) > > > > Which probably means I'll need to download Sun's preview 1.3 for > > Linux, it doesn't cause any problems with IBM's (should IBM's > > ClassLoader implementation be different from Sun's?). > > > > I'm currently investigating a classloader-related problem with Tomcat > 4.0 that shows up with 1.3 -- the app works under 1.2.2. I'll share > anything I learn here. > > > > > Just wanted to add that I hate ClassLoaders. > > +1 > > :-) > > > > > Stefan > > Craig McClanahan > > ==================== > See you at ApacheCon Europe <http://www.apachecon.com>! > Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing > Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ > Applications to Tomcat > > > >
