ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <>
Subject Re: ivy (2.3) and osgi
Date Tue, 31 Jan 2012 18:19:41 GMT

Le 31 janv. 2012 à 18:38, Richard Mauri a écrit :

> So is this statement from ivy trunk docs misleading/wrong or ?
> "You can also declare in your ivy.xml some OSGi dependency, 
> like a Require-Bundle, an Import-Package or an Import-Service, miming 
> My takeaway from this thread so far is that we must duplicate and invent some ad-hoc
mapping between ivy and bnd files.

For my point of view, and it is just mine, and it could probably change from your input because
I don't have much experience with managing OSGi dependencies. The workflow should be the following
* declare manually some dependencies in the ivy.xml so build a classpath. These dependencies
can be declared in the standard ivy way, while targeting an usual ivy/maven repository, or
declared in an OSGi way while targeting an OBR.
* then ivy download stuff and build a classpath of bundles; with that classpath you can build
you project, or even run the unit tests
* and with this classpath, bnd (with probably some little help of a bnd file) should be able
to generate a MANIFEST.MF so you can produce a bundle of your project. 

If I'm missing something, please let me know.


> Is it clear to anyone?
> -----Original Message-----
> From: David Goblirsch [] 
> Sent: Saturday, January 28, 2012 9:08 AM
> To:
> Subject: Re: ivy (2.3) and osgi
> Nicolas Lalevée wrote:
>> Le 27 janv. 2012 à 19:33, a écrit :
>>> 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
>> good to hear !
>> Nicolas
> 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?

View raw message