You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2011/04/11 10:21:05 UTC
[jira] [Created] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
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
[jira] [Commented] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018369#comment-13018369 ]
Andreas Pieber commented on KARAF-564:
--------------------------------------
thank you Gert :)
> 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
[jira] [Commented] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018301#comment-13018301 ]
Andreas Pieber commented on KARAF-564:
--------------------------------------
This may be a personal preference, but I prefer to scan through the property files and check what is possible than looking into the manual, but basically both is ok for me. AFAIK there was a plan some time ago to autogenerate the documentation for those settings?
> 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
[jira] [Closed] (KARAF-564) Allow configuring features OBR resolver
to resolve optional imports as well
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-564.
--------------------------------
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018296#comment-13018296 ]
Gert Vanthienen commented on KARAF-564:
---------------------------------------
Yeah, I was a bit reluctant to add the extra config file to the assembly since hardly anyone is using the features OBR support. I can obviously add it if you want, but perhaps we should start a config-guide in the manual project that really documents all the config PIDs and can have a description of all the configuration options available?
> 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
[jira] [Commented] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018274#comment-13018274 ]
Andreas Pieber commented on KARAF-564:
--------------------------------------
Maybe we could add a 'org.apache.karaf.features.obr.cfg' in Karaf's distribution setting resolveOptionalImports=false but documenting this option there? Otherwise I'm afraid this will become black-magic former or later :)
> 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
[jira] [Issue Comment Edited] (KARAF-564) Allow configuring
features OBR resolver to resolve optional imports as well
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018265#comment-13018265 ]
Gert Vanthienen edited comment on KARAF-564 at 4/11/11 10:01 AM:
-----------------------------------------------------------------
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1090998
and backported to 2.2.x branch in http://svn.apache.org/viewvc?view=revision&revision=1090999
Resolution of optional imports is not enabled by default, it requires a configadmin PID called 'org.apache.karaf.features.obr' to contain a setting 'resolveOptionalImports=true'
was (Author: gertvanthienen):
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1090998
and backported to 2.2.x branch in http://svn.apache.org/viewvc?view=revision&revision=1090999
Resolution of optional imports is not enabled by default, it requires a configadmin PID called {{org.apache.karaf.features.obr}} to contain a setting {{resolveOptionalImports=true}}
> 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
[jira] [Resolved] (KARAF-564) Allow configuring features OBR
resolver to resolve optional imports as well
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved KARAF-564.
-----------------------------------
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revision&revision=1090998
and backported to 2.2.x branch in http://svn.apache.org/viewvc?view=revision&revision=1090999
Resolution of optional imports is not enabled by default, it requires a configadmin PID called {{org.apache.karaf.features.obr}} to contain a setting {{resolveOptionalImports=true}}
> 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