You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/07/11 10:39:59 UTC

[jira] [Updated] (KARAF-658) Add "bundle blacklist"

     [ https://issues.apache.org/jira/browse/KARAF-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-658:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0
                   3.0.1

> Add "bundle blacklist"
> ----------------------
>
>                 Key: KARAF-658
>                 URL: https://issues.apache.org/jira/browse/KARAF-658
>             Project: Karaf
>          Issue Type: New Feature
>    Affects Versions: 2.1.5, 2.2.1, 3.0.0
>            Reporter: Andreas Pieber
>             Fix For: 3.0.1, 3.1.0
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira