Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: ivy (2.3) and osgi
Date: Tue, 31 Jan 2012 09:38:59 -0800
Message-ID: <3DDD5D9F240C2C4EB6641445773FD1380378BC12@us-hqmail5.ariba.com>
In-Reply-To: <4F242B57.8070305@interactivebrokers.com>
Thread-Topic: ivy (2.3) and osgi
Thread-Index: Aczd3xLjHt8TAoTOQY+Qx4zrc/+2NwCXuXPQ
References: <3DDD5D9F240C2C4EB6641445773FD1380337DFC4@us-hqmail5.ariba.com>
 <1463277305-1327689234-cardhu_decombobulator_blackberry.rim.net-1670806685-@b15.c11.bise7.blackberry>
 <AD4D2A60-DD77-42CF-A980-B3F2E09D4838@hibnet.org>
 <4F242B57.8070305@interactivebrokers.com>
From: "Richard Mauri" <rmauri@ariba.com>
To: <ivy-user@ant.apache.org>

So is this statement from ivy trunk docs misleading/wrong or ?

"You can also declare in your ivy.xml some OSGi dependency,=20
like a Require-Bundle, an Import-Package or an Import-Service, miming=20
an OSGi MANIFEST.MF."

My takeaway from this thread so far is that we must duplicate and invent =
some ad-hoc mapping between ivy and bnd files.

Is it clear to anyone?


-----Original Message-----
From: David Goblirsch [mailto:dgoblirsch@interactivebrokers.com]=20
Sent: Saturday, January 28, 2012 9:08 AM
To: ivy-user@ant.apache.org
Subject: Re: ivy (2.3) and osgi

Nicolas Lalev=E9e wrote:
> Le 27 janv. 2012 =E0 19:33, jerome.moliere@gmail.com a =E9crit :
>
>  =20
>> Hi richard
>> I set up a platform with about 350 bundles ...
>> I use plain ivy and I duplicated part from the meta information into =
bnd files to let ant generate the bundles using bnd task...
>> It has some overhead but it s clean and works nice
>>    =20
>
> good to hear !
>
> Nicolas
>
>  =20

I would like to not duplicate meta data in bnd template file if =
possible.

I already have rev information in my ivy file, so it would be nice if =
that
info could make it into the osgi manifest, e.g., OSGi version ranges in =
the
Import-Package:  based on the ivy rev attribute patterns.
E.g., have dependencies like commons-lang [2.6,3[, slf4j-api [1.6.3,)
get turned into properly structured OSGi version syntax.

Is this possible?