[
https://issues.apache.org/jira/browse/KARAF-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556846#comment-14556846
]
Christian Schneider commented on KARAF-3739:
--------------------------------------------
I was not thinking about embedding full event admin. Just the api package. Our
bundle would of course export and import the package to make sure there is only
one version used in the system. This would allow to start with no optional
packages.
I think optional packages are pretty problematic thing in OSGi. So I think
especially for a real core package like the feature service bundle it would be
good to avoid it.
I know the service is able to update itself but it is a pretty complicated
procedure. So I think it would be a good idea to not restart it just to install
event admin.
Of course we should still fix the core problem with the loop. I will try to
reproduce with pure karaf. Until now we just saw it when a lot of talend stuff
was also installed.
> Add eventadmin feature as featuresBoot in standard distribution
> ---------------------------------------------------------------
>
> Key: KARAF-3739
> URL: https://issues.apache.org/jira/browse/KARAF-3739
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0.M3
>
>
> In order to avoid shell console restart when installing eventadmin, and as
> lot of modules now uses eventadmin, it makes sense to install eventadmin
> feature by default in the standard distribution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
