Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (athena.apache.org: domain of aditsu@gmail.com designates
 64.233.170.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=K+ATdW+S7vyqHzJxIfDS2eti8SJECBi2UrEkO7Fvn8i33Ctj5f3Mz0VCpv2Bye13XN70jo/WIdthMkhijqXBboTsnKjLADcFUPmkc/Il/lDPR1W6mcV8HoraDMsyRGD7RJ57gRYjj6z8365tfM8+gVwhHrxdLJGHtbefHMxEi1U=
Message-ID: <83dae1610802141035r6b959eb6gc5d30bae4bffacf6@mail.gmail.com>
Date: Fri, 15 Feb 2008 02:35:29 +0800
From: "Adrian Sandor" <aditsu@gmail.com>
To: "Ant Developers List" <dev@ant.apache.org>
Subject: Re: [DISCUSS] release Ivy 2.0.0-beta2?
In-Reply-To: <635a05060802140921x77f59ddwb8c004c3d14a624e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2741_25638158.1203014129405"
References: <635a05060802100052t23c05cfase409a90ea0768fc6@mail.gmail.com>
	 <83dae1610802101118o5713ba9cu44a92124a751b290@mail.gmail.com>
	 <635a05060802101224w164aa22et511612f771318b9e@mail.gmail.com>
	 <83dae1610802102218l3c403d82necc72fa580028e84@mail.gmail.com>
	 <635a05060802110020m1e4f9aa8g99574cc64c0b42ff@mail.gmail.com>
	 <83dae1610802140040u7d992ae2xa1397fc43f2f3e5e@mail.gmail.com>
	 <635a05060802140056i1c12039fm62c8dad1580f1ed6@mail.gmail.com>
	 <83dae1610802140909ma390769j4079c9c68bef4e5e@mail.gmail.com>
	 <635a05060802140921x77f59ddwb8c004c3d14a624e@mail.gmail.com>

------=_Part_2741_25638158.1203014129405
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Xavier Hanin wrote:

> The cache element under the caches element is parsed automatically using
> the
> same logic as Ant tasks, using the Configurator class. At the beginning of
> the XmlSettingsParser class you have an array of configuration elements,
> including caches, which tells Ivy should auto configure the children. Then
> there'sa typdef.properties making the mapping between the "cache" element
> name and the DefaultRepositoryCacheManager class. But I suggest putting a
> breakpoint in the setName of this class and run a unit test doing some
> settings loading with cache related information, you'll better see what's
> happening.


Oh, I see now. It's a bit like Spring beans defined in xml.
I wonder why not all elements are parsed/configured in the same way. The
behavior is different too, e.g. undocumented attributes on the "caches"
element are ignored, but on the "cache" element they cause various errors.
<cache settings="your dog"/> is particularly interesting.
Anyway, thanks and sorry for the confusion :)

Adrian

------=_Part_2741_25638158.1203014129405--