karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seth Leger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5384) Optional dependencies in MINA SSHD Core cause system bundle refreshes
Date Fri, 22 Sep 2017 14:13:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176477#comment-16176477

Seth Leger commented on KARAF-5384:

My concern is that MINA is a very popular dependency and that many Karaf users may try to
install features that use it. The failure mode for this is *very* difficult to diagnose for
a casual Karaf user. It's very unexpected to see your SSH session disconnect or core bundles
restart or Pax Exam stop working just because you included MINA in a feature definition.

I would recommend that the Karaf project takes a proactive approach to problems like this
by repackaging core bundles with rewritten manifests that do not have optional dependencies,
or rewrite the core features so that all optional dependencies are installed for the core

> Optional dependencies in MINA SSHD Core cause system bundle refreshes
> ---------------------------------------------------------------------
>                 Key: KARAF-5384
>                 URL: https://issues.apache.org/jira/browse/KARAF-5384
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.1.0, 4.1.1, 4.1.2
>         Environment: Fedora Linux
>            Reporter: Seth Leger
>            Priority: Critical
>             Fix For: 4.1.3
> In similar fashion to KARAF-5251, if you install any feature in Karaf that includes:
> - Apache MINA
> - bouncycastle
> - net.i2p.crypto
> it will cause the MINA SSHD Core bundle to refresh, which in turn refreshes most of the
core framework bundles. This has a variety of bad effects including:
> - Terminating the current SSH session
> - Terminating subsequent feature installations
> This is more severe than KARAF-5251 because these libraries are not part of the core
Karaf distro so it is not possible to add them to {{startup.properties}} without first repackaging
Karaf to contain the desired bundles in the {{/system}} directory.
> This also makes testing any Karaf feature that contains MINA, bouncycastle, or net.i2p.crypto
impossible in Pax Exam (unless you use org.apache.karaf.features.FeaturesService.Option.NoAutoRefreshBundles
or feature:install -r) because the refresh invalidates @Inject references in your test as
the core bundles are refreshed.

This message was sent by Atlassian JIRA

View raw message