wouldn't it be better to include the public ivysettings in your
project-specific ivysettings file (instead of the other way around), and do the
override logic that way? the "override" features requires that you know ahead
of time what is going to be overridden in the parent file. This will ten
On 2009-06-09, Maarten Coene wrote:
> Or maybe we can create an extra Ant distribution which contains the
> standard Ant tasks + Ivy (+ other antlibs?)
We sure can, I think we should talk about that when we seriously start
thinking about the next release of Ant.
Stefan
The ivy configuration I am currently have is where all projects include a
global ivy settings file, which is pretty much the same as the default ivy
settings. (The whole setup is like the multi-project example but using our own
set of global ivy settings files)
Here is the dump of the resolver
