Hi,
Also, while the OSGi spec would allow two bundles with the same symbolic name
but different versions to be installed, it easy to break this setup if export
and import versions are not properly specified.
Therefore all tooling coming out fo Sling (JCR/OSGi Installer and Web Console)
don't s
The new commons libs are unfortunately not compatible to the old ones
but use the same symbolic name. So far, we created wrapper bundles
which use a different symbolic name for one of them to avoid this
problem.
Regards
Carsten
2012/2/9 Ian Boston :
> Ok, no worries.
> Thanks
> Ian
>
> On 9 Febru
Ok, no worries.
Thanks
Ian
On 9 February 2012 13:32, Justin Edelson wrote:
> No, this is not supported. The second version overrides the first. I
> supposed we could add some extra metadata to the second item to
> indicate that it was not supposed to replace the first item, but I
> doubt we could
No, this is not supported. The second version overrides the first. I
supposed we could add some extra metadata to the second item to
indicate that it was not supposed to replace the first item, but I
doubt we could figure this out automagically.
Justin
On Wed, Feb 8, 2012 at 7:23 PM, Ian Boston
Hi,
Should the launchpad pluging be able to plackage multiple versions of
the same jar ?
The current BND tool has become quite expressive on version ranges for
major numbers (correctly[1]), but where 2 versions of the same jar can
exist in an OSGi container[2], the launchpad plugin doesn't appear t
