camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-3763) Update Camel features descriptor to be Karaf 2.2.0 compliant
Date Tue, 05 Apr 2011 22:52:06 GMT


Gert Vanthienen commented on CAMEL-3763:

Took an initial stab at marking stuff as a dependency in

Marking a bundle as a dependency allows the OBR resolver to skip that exact bundle if it can
reuse a previously installed bundle to provide the required imports.  I marked normal OSGi
bundles, specification bundles and common bundles like Spring stuff as dependencies.  I tried
to avoid marking any implementations for specs as a dependency, as the other bundles will
only import the specification packages we need to keep those implementations  explicitly listed
as the OBR resolver won't look for them.

Could someone take another look at this commit to ensure I didn't do anything wrong there?

> Update Camel features descriptor to be Karaf 2.2.0 compliant
> ------------------------------------------------------------
>                 Key: CAMEL-3763
>                 URL:
>             Project: Camel
>          Issue Type: Task
>          Components: karaf
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.8.0
>         Attachments: CAMEL-3763.patch, CAMEL-3763.patch
> To be compliant with Karaf 2.2.0, the Camel features descriptor will be update:
> - to avoid to override the Aries blueprint bundle
> - to not define Karaf external repository
> - to use the OBR resolver

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message