karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-658) Add "bundle blacklist"
Date Mon, 25 Jan 2016 12:52:39 GMT

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

Jean-Baptiste Onofré commented on KARAF-658:

In Karaf 4, thanks for the resolver, the impact should be limited now. I would prefer to avoid
to introduce a property dedicated for bundles "inside" features. Resolver and resource repositories
should be able to deal with that.

> Add "bundle blacklist"
> ----------------------
>                 Key: KARAF-658
>                 URL: https://issues.apache.org/jira/browse/KARAF-658
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-core, karaf-osgi
>    Affects Versions: 2.1.5, 2.2.1, 3.0.0
>            Reporter: Andreas Pieber
>              Labels: low-hanging-fruit
> Today I've encountered the interesting problem that Karaf reacts VERY strangely if "mvn:org.osgi/org.osgi.core/4.2"
is added to a feature file. The reason for the problem is clear; though to avoid that such
errors lead to "Karaf going crazy" we should add the option of a bundle-blacklist to etc/org.apache.karaf.features.cfg:
> {code}
> bundleBlacklist=org.osgi/org.osgi.core
> {code}
> If someone, for any reason really knows what he is doing and still like to install the
bundle he can simply manipulate the blacklist. Otherwise we could simply ignore such bundles
during reading of feature files.

This message was sent by Atlassian JIRA

View raw message