Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: softfail (nike.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 v1081)
Subject: Re: Import Bushel into Ivy
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <26510.49815.qm@web30806.mail.mud.yahoo.com>
Date: Tue, 19 Oct 2010 09:51:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <34A182A1-DF13-440E-A2DA-691766048530@hibnet.org>
References: <B53D948C-5DA9-48D8-B81D-2F8C44DBA969@hibnet.org>
 <26510.49815.qm@web30806.mail.mud.yahoo.com>
To: "Ant Developers List" <dev@ant.apache.org>


Le 18 oct. 2010 =E0 23:54, Maarten Coene a =E9crit :

> +1 for me. There is a chance I'm going to use OSGi @ work, so this =
could be a=20
> good test case :-)
>=20
> I've noticed the code is not JDK 1.4 compatible, but I guess it won't =
be a=20
> problem to downgrade it?
> Or maybe we should drop the JDK 1.4 requirement for Ivy, but I would =
rather not=20
> do that as long as Ant is also 1.4 compatible.

I prefer to keep Ivy JDK 1.4 compatible too, for the same reason. I'll =
downgrade the code.

Nicolas


>=20
> Maarten
>=20
>=20
>=20
> ----- Original Message ----
> From: Nicolas Lalev=E9e <nicolas.lalevee@hibnet.org>
> To: Ant Developers List <dev@ant.apache.org>
> Sent: Wed, October 13, 2010 3:38:33 PM
> Subject: Import Bushel into Ivy
>=20
> Hi all,
>=20
> I would like to import the code of Bushel [1] into Ivy core.
>=20
> On the technical part.
> Bushel implement some special Ivy resolver and version matching which =
understand=20
> the different kind of OSGi dependency, and also understand the =
repository=20
> descriptor OBR (OSGi Bundle Repository). So the import will make those =
resolver=20
> part of Ivy core.
>=20
> On the legal part.
> The code has been developed under the ASL2 license and by only three=20=

> developpers: Alex Radeski, J=E9r=F4me Benois and me. I have contacted =
the two=20
> others, they are joining me in this request and are willing to sign =
any software=20
> grant paper necessary.
> As the code will be imported into Ivy, the "Bushel" name will then =
disappear.=20
> Ivy will then support some OSGi feature.
>=20
> Deeper in the technical part.
> As I explained here [2], Ivy cannot fulfill entirely the OSGi resolve=20=

> specification. But I have managed to make resolve work and I think it =
can fill=20
> some requirement like making some transition from a ivy/maven based =
resolution=20
> mechanism to a pure OSGi based one. Or the reverse. With that respect, =
we=20
> shouldn't lure Ivy users to say that Ivy support OSGi and I suggest =
that we=20
> would flag at first it as "experimental". As users would start to try =
it, we=20
> will see real world case appear, and then we would then advise of its =
real=20
> state.
> This might sound quite pessimistic, but I find this feature exiting =
enough to=20
> bring it into Ivy core.
>=20
>=20
>=20
> WDYT ?
>=20
> Nicolas
>=20
> [1] http://code.google.com/p/bushel/
> [2] http://code.google.com/p/bushel/wiki/IvyOsgiMapping
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20
>=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org