[
https://issues.apache.org/jira/browse/KARAF-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556834#comment-14556834
]
Guillaume Nodet commented on KARAF-3739:
----------------------------------------
I don't like the idea of embedding eventadmin in the features-core bundle.
It's really an optional component, so embedding it to solve a bug is not a good
idea.
In addition, if people actually start using the "static distributions" in which
all bundles are pre-installed, the features service is not needed anymore.
Christian, if you can reproduce your infinite loop problem, give me the way to
reproduce it and i'll fix it.
In theory (and in practice as far as I've seen), the features service is able
to update itself. The shell can be restarted if the wiring of the shell
bundles has changed, but it's the same as any other bundle, it's only a bit
more visible to the user (at least when you install the features from the
shell), however, this should cause no real problems (and the refresh can be
avoided by passing the correct argument to the command afaik).
I'd really rather fix any real problem than embedding event admin.
If the problem you mention comes from the fact that the eventadmin is installed
at boot time instead of startup time, we can move it to that stage to avoid the
refresh of the features service.
> 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)
