Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 85678 invoked by uid 500); 10 May 2001 14:44:42 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 85522 invoked from network); 10 May 2001 14:44:34 -0000 Date: Thu, 10 May 2001 07:34:37 -0700 (PDT) Message-Id: <200105101434.HAA18488@nagoya-a.betaversion.org> From: bugzilla@apache.org To: ant-dev@jakarta.apache.org, kario@mermit.fi Cc: Subject: [Bug 1556] Changed - ClassLinkageError while testing classes which use JAXP classes X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1556 *** shadow/1556 Fri Apr 27 09:14:52 2001 --- shadow/1556.tmp.18485 Thu May 10 07:34:37 2001 *************** *** 2,8 **** | ClassLinkageError while testing classes which use JAXP classes | +----------------------------------------------------------------------------+ | Bug #: 1556 Product: Ant | ! | Status: NEW Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Linux | | Priority: Low Component: Optional Tasks | --- 2,8 ---- | ClassLinkageError while testing classes which use JAXP classes | +----------------------------------------------------------------------------+ | Bug #: 1556 Product: Ant | ! | Status: ASSIGNED Version: 1.3 | | Resolution: Platform: PC | | Severity: Normal OS/Version: Linux | | Priority: Low Component: Optional Tasks | *************** *** 81,84 **** Happy bughunting... Janne Kario ! --- 81,97 ---- Happy bughunting... Janne Kario ! ! ! ------- Additional Comments From conor@cortexebusiness.com.au 2001-05-10 07:34 ------- ! Can you try forking the junit task (running junit with fork="yes"). You'll need ! to add the ant junit classes into the classpath when you do. ! ! Your analysis is close to the mark. The classes when they are loaded are ! violating loader constraints. These come about when a class in one loader ! refers to methods or fields in a class loaded by another loader. It is ! difficult to avoid when the package namespaces of the classloaders (system and ! junit task) overlap. ! ! Forking is usually effective. If so, please let me know and I will close this ! bug.