karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gert Vanthienen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-564) Allow configuring features OBR resolver to resolve optional imports as well
Date Mon, 11 Apr 2011 12:03:05 GMT

    [ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018309#comment-13018309

Gert Vanthienen commented on KARAF-564:

Added the missing config file in http://svn.apache.org/viewvc?view=revision&revision=1091047
for trunk
and http://svn.apache.org/viewvc?view=revision&revision=1091048 for the 2.2.x branch

> Allow configuring features OBR resolver to resolve optional imports as well
> ---------------------------------------------------------------------------
>                 Key: KARAF-564
>                 URL: https://issues.apache.org/jira/browse/KARAF-564
>             Project: Karaf
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 2.2.1, 3.0.0
> In ServiceMix, we started leveraging the features OBR resolver functionality to avoid
installing excess bundles when we combine features from other projects (like ActiveMQ, Camel
and CXF) with our own descriptors.  Some of our bundles have quite a few optional imports,
and if we want to allow users to use these optional bits, we have to ensure that none of the
providing bundles has "dependency=true" set on them.  It would be nice if the OBR resolver
itself could be configured to also look for optional imports instead, as this would make the
features a lot easier to maintain.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message