[ https://issues.apache.org/jira/browse/KARAF-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175884#comment-16175884 ]
Freeman Fang commented on KARAF-5384: ------------------------------------- hmm.... Not sure if this is something we need fix in default karaf kit FYI, 1. you can use command like {code} feature:install -r {code} to avoid the refreshment or 2. you can build a customized karaf kit where you can install all optional bundles for MINA SSHD CORE beforehand Freeman > 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 (v6.4.14#64029)