On Thu, Feb 14, 2008 at 6:09 PM, Adrian Sandor <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 14, 2008 at 4:56 PM, Xavier Hanin wrote: > > > > Would you like me to work on it? Or add a comment to IVY-399? > > > > I think we have a little less than a week before we cut the beta2. If > you > > can do the job (code, reference doc and junit changes) in this > timeframe, > > it's more than welcome! > > > Well, I'm working on it. I plan to move *ALL* the cache-related attributes > to the "caches" element (but I'm still keeping the 1.x ones as > deprecated), > let me know if there's any problem. > Anyway, I noticed that the "cache" element is wonderfully documented, > but.. > is completely missing from the code! If I'm wrong, could you show me where > it's getting parsed? 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. HTH, Xavier > > > Thanks > Adrian > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
