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.166.181 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=dbhalUk5X6yq9gPxeb3y1JtE6/nT1mE18DMc5MlbpKjmO3jmrcNvwBStHMGKkU24QyTSZhHBjOj/AP3Zqwyj/wMd+EF6CNWorWhPH2KecXXfnWASmcUfmG0pvUh+Df6C7gedz9ByWmabpi2dXNBpa76UchPtFYKbQH3wAOuf3Ro=
Message-ID: <83dae1610802102218l3c403d82necc72fa580028e84@mail.gmail.com>
Date: Mon, 11 Feb 2008 14:18:51 +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: <635a05060802101224w164aa22et511612f771318b9e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4321_20387080.1202710731402"
References: <635a05060802100052t23c05cfase409a90ea0768fc6@mail.gmail.com>
	 <83dae1610802101118o5713ba9cu44a92124a751b290@mail.gmail.com>
	 <635a05060802101224w164aa22et511612f771318b9e@mail.gmail.com>

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

On Feb 11, 2008 4:24 AM, Xavier Hanin wrote:

> > - 3 tags for cache configuration: settings, caches and cache
>
> The settings on the settings tag are mainly due to legacy. We could indeed
> deprecate them to move all cache settings to the caches element. cache
> element should now only the defition of one cache, so I don't see how we
> could avoid that.


I also said "cache" tags could be ok as they are now. Two tags (caches and
cache) are acceptable.


> > - inconsistent/confusing attributes on the settings tag: defaultCache
> and
> > resolutionCacheDir - different naming styles although they're both
> > directories; and both of them specify the resolution cache but
> > defaultCache
> > also specifies the repository cache?
>
> Yes, this is a legacy problem, but I agree it's confusing. Maybe we can
> rename it to defaultCacheDir, and deprecate defaultCache.


So, if I understand correctly, right now settings/defaultCache is the
default for both resolution and repository cache;
settings/resolutionCacheDir overrides it for resolution, caches/basedir
overrides it for repository, and cache/basedir overrides caches/basedir (for
repository).
Perhaps we can move settings/resolutionCacheDir to
caches/resolutionCacheDir, rename caches/basedir to
caches/repositoryCacheDir, and either remove settings/defaultCache or move
it to caches/defaultCacheDir.


> > - some confusion between "defaultCache" on settings, "default" on
> caches,
> > and "default-cache"
>
> Again, if we rename defaultCache in defaultCacheDir, I think this would be
> less confusing. Would this be enough in your opinion?


It would definitely help. Probably good enough, if the docs are clear.


> > - ivy and artifact patterns everywhere
>
> What's the problem with that? Could you elaborate?


settings/cacheIvyPattern and settings/cacheArtifactPattern vs
caches/ivyPattern and caches/artifactPattern, they're redundant.

Also these have changed since beta 1 (cache/repositoryIvyPattern and
cache/repositoryArtifactPattern), and so did the resolution/repository dir
attributes. Change itself is not bad, we should just make sure the new way
is really better.

Adrian

------=_Part_4321_20387080.1202710731402--