Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 19672 invoked from network); 25 Feb 2002 08:02:06 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 Feb 2002 08:02:06 -0000 Received: (qmail 2914 invoked by uid 97); 25 Feb 2002 08:02:10 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 2888 invoked by uid 97); 25 Feb 2002 08:02:09 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 2877 invoked from network); 25 Feb 2002 08:02:08 -0000 Message-ID: <004f01c1bdd2$be1b0c30$d1eefea9@homenkf0y0hwu0> Reply-To: "Stephane Bailliez" From: "Stephane Bailliez" To: "Ant Developers List" References: <20020224140240.65846.qmail@apache.org><00b501c1bd40$5cd0f800$d1eefea9@homenkf0y0hwu0><001501c1bd44$76d1c7d0$6601a8c0@darden.virginia.edu><00d301c1bd49$b157ad20$d1eefea9@homenkf0y0hwu0><007001c1bd61$7c8fc9c0$1502a8c0@Stelvio> Subject: Re: [GUMP] Test Failure - Ant Date: Mon, 25 Feb 2002 09:02:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Stefan Bodewig" > > I'd suspect Stephane's change to set the context classloader when > running - Gump's classpath handling is different from the > handling you get when running the tests yourself, it sets > build.sysclasspath to only. > > My guess - I need to investigate this further - is that Xerces' parser > factory uses the context class loader to load the parser > implementation and fails because some classes or interfaces end up > being loaded via different classloaders. mmm... indeed this is certainly related. what is the logic used for the ant classloader ? I think that it should *never* pickup any jar in the parent classloader (mm..at least system classloader) but in the situation of build.sysclasspath only. maybe we need to do something more like tc3.3/tc4 classloader schema: having a system/ant/common/app classloaders... One thing that was surprising however is that the first time I did the run, I had load of class not found related to CMany in xerces or something like that, I rerun the test. nothing. I tried to set the same classpath config. nothing. No idea where this one was coming from and could not reproduce it. Stephane -- To unsubscribe, e-mail: For additional commands, e-mail: