[
https://issues.apache.org/jira/browse/CAMEL-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649709#comment-14649709
]
Dhiraj Bokde commented on CAMEL-9039:
-------------------------------------
So Karaf supports loading bundles and config on the condition that some other
feature is already installed. It is used in Karaf to conditionally load its own
features, when the {{shell}} feature is loaded, the same thing we want to do
for camel-core.
I have committed the change to add the same conditional check around bundles
{{camel-commands-core, camel-karaf-commands}} and left {{camel-catalog}} as it
is for tooling support. So if camel-core is loaded in a karaf container with
{{shell}} feature, the command bundles will be loaded, otherwise they won't.
This way existing karaf containers won't be affected, and we don't have to
worry about all the component features that load {{camel-core}} feature.
> Feature camel-core contains bundles, which should be made optional for
> micro-services deployment
> ------------------------------------------------------------------------------------------------
>
> Key: CAMEL-9039
> URL: https://issues.apache.org/jira/browse/CAMEL-9039
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.15.2
> Reporter: Dhiraj Bokde
> Assignee: Dhiraj Bokde
>
> The camel-core feature loads the following bundles that are only useful in a
> console based karaf container:
> {code}
> <bundle>mvn:org.apache.camel/camel-catalog/${project.version}</bundle>
> <bundle>mvn:org.apache.camel/camel-commands-core/${project.version}</bundle>
> <bundle>mvn:org.apache.camel.karaf/camel-karaf-commands/${project.version}</bundle>
> {code}
> Loading these bundles should be made optional so that the camel-core feature
> (and all the component features that depend on it) can be easily used in a
> micro-services deployment of Karaf4.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
