ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <nicolas.lale...@hibnet.org>
Subject Re: ivy (2.3) and osgi
Date Tue, 31 Jan 2012 18:09:13 GMT

Le 28 janv. 2012 à 18:07, David Goblirsch a écrit :

> Nicolas Lalevée wrote:
>> Le 27 janv. 2012 à 19:33, jerome.moliere@gmail.com 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.

The Import-Package dependencies have a different version scheme from the Require-Bundle ones.
So one is not translatable into the other.
I guess bnd could do something about it, but only if there is some version information in
the manifest of commons-lang. Is there some ?

Nicolas


Mime
View raw message