Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Content-Class: urn:content-classes:message
Subject: Core classloader (1.7)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C3DB75.96573FC6"
Date: Thu, 15 Jan 2004 14:40:57 -0000
Message-ID: <747F247264ECE34CA60E323FEF0CCC0C5D0964@london.cellectivity.com>
Thread-Topic: Core classloader (1.7)
thread-index: AcPbdZZECgwp5JoNSFiCz77qop27gg==
From: "Jose Alberto Fernandez" <jalberto@cellectivity.com>
To: <dev@ant.apache.org>

------_=_NextPart_001_01C3DB75.96573FC6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi, I was looking at how to better reuse the classloaders
(as part of the fixes for JAXPUtils).

In the process I noticed that Project.createClassLoader(Path)
does not set Project.getCoreLoader() as the parent of the classloader
being created.=20

Actually, except for ExecuteJava.java and WhichResource.java
no task that uses its own classpath for finding code will=20
set the core loader as the parent for the classloaders.

Most stuff works because AntClassLoader.class.getClassLoader() is
usually the same as the initial Project.getCoreLoader().
But you may have extrange behavior in some complex IDE situations.

Any comments, reasons why the code is the way it is?

Jose Alberto


------_=_NextPart_001_01C3DB75.96573FC6
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
------_=_NextPart_001_01C3DB75.96573FC6--