On Tuesday 30 December 2003 07:35, Stephen McConnell wrote: > Olaf Bergner wrote: > > Switched to AMTC just for verification > > and got the exact same LinkageError. > > It so far out! > > Thing is that I have never seen this before. > Anyway - we will have JIRA up and runing shortly - you'll be able to > register a bug and test case!
I haven't seen LinkageError either in a long time... My Guts (main debugging device) indicates that you could have a problem along these lines; When JUnit runs, each method involves the recreation of the object, including calling the tearDown() and setUp() methods. This must be a key aspect of the problem. So my gut suspects, that the testcase triggers a reload of some classes in a classloader from a different location than is already present somewhere else in the classloading hierarchy. Alternatively, a classloader that is expected to have been completely dropped, is still around and its loaded classes creates the conflict. My angle of attack would be; 1. Make sure I clean out all the Avalon-related repository entries. 2. After a new LinkageError, ensure that there are only one set of Avalon-related repository entries on my entire system. 3. If that is "Ok", just prior to the LinkageError, insert a ClassLoader and Thread traversal and printout of the URLs used. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
