[
https://issues.apache.org/jira/browse/KARAF-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14556865#comment-14556865
]
Guillaume Nodet commented on KARAF-3739:
----------------------------------------
Ok, that makes more sense.
However, I'm not sure to fully buy the solution, as having multiple bundles
exporting the same package can lead to wiring problems too in case the resolver
ends actually exporting the package multiple times. When the packages can be
controlled, I'd rather avoid multiple copies...
I'm not really sure what the behaviour would be in such case, if you install
the eventadmin feature while the package is already exported by features-core.
You may very well end-up with the same refresh...
Doesn't the first proposed solution solve the problem ? i.e. install eventadmin
as a startup feature in the default distribution. It's a very simple change
(just adding a line to the pom) and should minimise problems down the road (no
package duplicated, no refresh needed, etc...).
> 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)
