[DISCUSS] Version ranges in imported packages by wrapper bundles

[Łukasz Dywicki <lu...@code-house.org>]

Dear all,
The wrapper bundles we create in many cases have other non-osgi compatible dependencies. Some of them have other wrapper bundles. This leads us to situation when we wrap bundle and produce half-functional headers. For example we calculate uses directive but we do not specify ranges for imported packages. So there is a proposal to start providing import ranges where we can starting from new and updated bundles in next releases. This will require some more work during creation of new bundles and upgrade process will also be harder.

Cheers,
Łukasz Dywicki
--
luke@code-house.org
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org

Re: [DISCUSS] Version ranges in imported packages by wrapper bundles

[Jean-Baptiste Onofré <jb...@nanthrax.net>]

Hi Lukasz,

In the latest bundles that I created, I always use dependency:tree to 
analyse the dependencies and add version range in import.

I didn't update all previous bundles that way.

Regards
JB

On 07/03/2013 10:30 AM, Łukasz Dywicki wrote:
> Dear all,
> The wrapper bundles we create in many cases have other non-osgi compatible dependencies. Some of them have other wrapper bundles. This leads us to situation when we wrap bundle and produce half-functional headers. For example we calculate uses directive but we do not specify ranges for imported packages. So there is a proposal to start providing import ranges where we can starting from new and updated bundles in next releases. This will require some more work during creation of new bundles and upgrade process will also be harder.
>
> Cheers,
> Łukasz Dywicki
> --
> luke@code-house.org
> Twitter: ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com