Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Tue, 10 Oct 2017 10:32:00 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.13103696.1505933744000.16728.1507631520347@Atlassian.JIRA>
In-Reply-To: <JIRA.13103696.1505933744000@Atlassian.JIRA>
References: <JIRA.13103696.1505933744000@Atlassian.JIRA> <JIRA.13103696.1505933744186@jira-lw-us.apache.org>
Subject: [jira] [Commented] (KARAF-5384) Optional dependencies in MINA SSHD
 Core cause system bundle refreshes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 10 Oct 2017 10:32:05 -0000


    [ https://issues.apache.org/jira/browse/KARAF-5384?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1619=
8491#comment-16198491 ]=20

Jean-Baptiste Onofr=C3=A9 commented on KARAF-5384:
---------------------------------------------

The only workaround I see is more documenting and warn users that this refr=
esh will happen. I don't see how to avoid this as it doesn't make sense to =
ship mina as "core" Karaf dependency.

> 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
>            Assignee: Jean-Baptiste Onofr=C3=A9
>            Priority: Critical
>             Fix For: 4.1.4
>
>
> In similar fashion to KARAF-5251, if you install any feature in Karaf tha=
t includes:
> - Apache MINA
> - bouncycastle
> - net.i2p.crypto
> it will cause the MINA SSHD Core bundle to refresh, which in turn refresh=
es most of the core framework bundles. This has a variety of bad effects in=
cluding:
> - 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.pro=
perties}} without first repackaging Karaf to contain the desired bundles in=
 the {{/system}} directory.
> This also makes testing any Karaf feature that contains MINA, bouncycastl=
e, or net.i2p.crypto impossible in Pax Exam (unless you use org.apache.kara=
f.features.FeaturesService.Option.NoAutoRefreshBundles or feature:install -=
r) because the refresh invalidates @Inject references in your test as the c=
ore bundles are refreshed.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)