Return-Path: <jak-ant-dev@m.gmane.org>
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 4558 invoked from network); 3 Mar 2003 19:53:30 -0000
Received: from main.gmane.org (80.91.224.249)
  by daedalus.apache.org with SMTP; 3 Mar 2003 19:53:30 -0000
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18pvza-0006Tl-00
	for <dev@ant.apache.org>; Mon, 03 Mar 2003 20:52:54 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: dev@ant.apache.org
Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 18pvyz-0006RA-00
	for <gmane-comp-jakarta-ant-devel@m.gmane.org>;
 Mon, 03 Mar 2003 20:52:17 +0100
From: Costin Manolache <cmanolache@yahoo.com>
Subject: Re: ClassLoader and Properties handling behaviour
Date: Mon, 03 Mar 2003 11:45:57 -0800
Lines: 22
Message-ID: <b40bpg$o53$1@main.gmane.org>
References: <1046543431.4159.462.camel@localhost.localdomain>
 <3E634C17.7040207@cortexebusiness.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet@main.gmane.org
User-Agent: KNode/0.7.2
Sender: news <news@main.gmane.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Conor MacNeill wrote:

> Also, I'm a little concerned about violating the classloading hierarchy -
> it leads to Linkage errors in my experience. I have the same concern with
> the ClassLoader task.

The ClassLoader task is no longer using the classloading hierarchy - the
initial version did, and it resulted in the expected Linkage errors ( and 
related workarounds ). This was needed in [embed] to work around ant1.5 
limitations - but when I merged I removed all the hacks, they are not needed
in 1.6.

By default it'll just add more jars to the main ant loader - and rely on the
lazy creation of tasks.

The <classloader> task can be extended to deal with hierarchies and
direct/reverse delegation - but the most common use will be to extend the
main ant loader.



Costin