Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@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 v1084)
Subject: Re: ivy (2.3) and osgi
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <3DDD5D9F240C2C4EB6641445773FD1380337DFC4@us-hqmail5.ariba.com>
Date: Sat, 28 Jan 2012 13:04:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <642FC742-A428-4121-9E38-22A81509461B@hibnet.org>
References: <3DDD5D9F240C2C4EB6641445773FD1380337DFC4@us-hqmail5.ariba.com>
To: ivy-user@ant.apache.org


Le 27 janv. 2012 =E0 19:13, Richard Mauri a =E9crit :

> Greetings, we are investigating alternatives to building osgi bundles
> (and resolving/retrieving bundles for ease of copying to
> virgo-tomcat/repository/usr) in an "ivy-first" approach.
>=20
>=20
>=20
> I found the following docs which encourage me and I'd love to get
> started with this and help if need be.
>=20
>=20
>=20
> According to http://ant.apache.org/ivy/history/trunk/osgi.html
>=20
> So with a standard ivy.xml, you can express some dependency on some =
OSGi
> bundle and every of their trasitive dependencies will be resolved. You
> can also declare in your ivy.xml some OSGi dependency, like a
> Require-Bundle, an Import-Package or an Import-Service, miming an OSGi
> MANIFEST.MF.
>=20
>=20
>=20
> According to
> http://ant.apache.org/ivy/history/trunk/osgi/standard-osgi.html
>=20
> In oder to produce OSGi metadata of suffient quality and to avoid
> maintaining them manually, the bnd <http://www.aqute.biz/Code/Bnd>  =
tool
> will be used. The approach taken is then an "Ivy file first" approach.
> The dependencies will be specified in the ivy.xml file, the =
MANIFEST.MF
> being generated from the computed classpath.
>=20
>=20
>=20
> Then, on the other hand I see this support for manifest-first docs:
>=20
> According to
> http://ant.apache.org/ivy/history/trunk/osgi/osgi-mapping.html
>=20
> there is early experimental work to map osgi manifest first to =
generated
> ivy.xml
>=20
>=20
>=20
> Also http://ant.apache.org/ivy/history/trunk/use/convertmanifest.html
>=20
> since 2.3 Convert a MANIFEST.MF into an ivy.ml file
>=20
>=20
>=20
> Sigh.. no mention of any sort of genbnd or genmanifest ant tasks

The bnd should be wrote by yourself. If you don't have a too much =
complicated classpath, it will be probably mostly empty. Actually the =
one in the example is empty on purpose.
Then the task about generating the MANIFEST.MF is the bnd one, see the =
target "generate-manifest" in the build.xml of the example.
You can download the bnd task there: http://www.aqute.biz/Code/Bnd

Nicolas