Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted
 sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Build 2.2.0.final_20110323150448 and update site?
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <BLU0-SMTP31966A6C3C468B7C3240ADC5B90@phx.gbl>
Date: Wed, 30 Mar 2011 18:37:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F99D6B09-6A7E-4A46-9FBE-1040A4350547@hibnet.org>
References: <BLU0-SMTP31966A6C3C468B7C3240ADC5B90@phx.gbl>
To: ivy-user@ant.apache.org


Le 26 mars 2011 =E0 00:15, Andre-John Mas a =E9crit :

> Hi,
>=20
> When should we expect build 2.2.0.final_20110323150448 to make it to =
the update site?
>=20
> Build 2.2.0.final_20110323150448 provides the option to "auto map jar =
artifacts with unique source artifact", meaning that if the source jar =
name is not an exact match to the binary, I will still be able to have =
the source associated with the binary, which is something I find very =
useful. I wouldn't have known about this had it not been for someone on =
the "Ivy Roundup" site. I installed it manually so I could have it, but =
I am curious if it is indeed to be considered a "stable build" ready for =
the main update site.

In the 2.2, there are some big change in the way the resolve is =
launched, and the way retrieved artifacts are managed. So the next =
version will probably be a 2.2 beta.

I use the 2.2 myself for my day job. So it works great at least for my =
use case.

To get an official 2.2 out (probably beta for the first one), I have a =
couple of issue I would want to address before, and I don't know when =
I'll have time to get into it. Maybe we'll have a release next next =
month.

Nicolas