ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <>
Subject Re: Ivy settings id (was Re: Merge 641903 from trunk to 1.7 branch?)
Date Fri, 28 Mar 2008 16:50:08 GMT
On Fri, Mar 28, 2008 at 5:14 PM, Dominique Devienne <>

> On Fri, Mar 28, 2008 at 10:31 AM, Xavier Hanin <>
> wrote:
> > On Fri, Mar 28, 2008 at 4:08 PM, Dominique Devienne <
> >
> >  > For the record, I think it's bad Ant style to use ids in tasks. [...]
> >
> >  I think we use that bad pattern. We've been wondering about the best
> form
> >  settings should take for a while. It used to be a datatype in 2.0alpha, but
> >  we were running into trouble because a datatype has no lifecycle. Hence
> in a
> >  discussion  Peter suggested to make it a task, using the id as we did
> before
> >  for the datatype but with a default value:
> >
> Well, reading Gilles original issue, I agree with your answer Xavier.
> The "Ant way"(tm) is to have both an id for the <settings> and a
> settingsRef in <retrieve>.
> The only reason you'd not have a settingsRef in <retrieve> was to be
> BC with the deprecated <config> task,

Well, it's not fully a BC issue. We could keep the configure task for BC,
and define settings however we want since it's new in 2.0. The problem is
more related to Ivy design. In Ivy original design I tried to make using Ivy
as easy as possible. Hence if you want to use the default settings, and have
an ivy file called ivy.xml in your basedir, then using Ivy is as simple as:
<ivy:retrieve />

I think this has been appreciated by our users from the beginning of Ivy.
Behind the scene, this is roughly equivalent to:
<ivy:configure />
<ivy:resolve />
<ivy:retrieve />

But I don't know if people would complain if we were now using the settings
as any other datatype in the "Ant way". But I think that actually loading
the settings only when they are used is counter intuitive... maybe because
I'm too biased by usage of current Ivy design for more than 3 years now. So
I think this is a difficult design choice: make Ivy more compliant with the
Ant way, or keep a usage as it is used by some people for years, people who
haven't complained about this point yet AFAIR. It's difficult to choose, and
it's probably why we have discussed this so many times so far.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message