[
https://issues.apache.org/jira/browse/KARAF-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556873#comment-14556873
]
Christian Schneider edited comment on KARAF-3739 at 5/22/15 9:37 PM:
---------------------------------------------------------------------
Adding eventadmin as a stage 1 boot feature indeed solves the problem. I am
just a bit concerned that people who create a custom distro might remove the
eventadmin feature again and get into the same situation if some user installs
it again for his deployment. After all it will not be obvious why we added the
eventadmin feature.
was (Author: [email protected]):
Adding eventadmin as a boot feature indeed solves the problem. I am just a bit
concerned that people who create a custom distro might remove the eventadmin
feature again and get into the same situation if some user installs it again
for his deployment. After all it will not be obvious why we added the
eventadmin feature.
> 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)
