Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not A Problem
    • Affects Version/s: 2.1.5, 2.2.1, 3.0.0
    • Fix Version/s: None
    • Component/s: karaf-core, karaf-osgi

      Description

      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:

      bundleBlacklist=org.osgi/org.osgi.core
      

      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.

        Activity

        Hide
        Jean-Baptiste Onofré added a comment -

        As discussed on IRC, it looks good to me.

        Show
        Jean-Baptiste Onofré added a comment - As discussed on IRC, it looks good to me.
        Hide
        Jean-Baptiste Onofré added a comment -

        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.

        Show
        Jean-Baptiste Onofré added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Andreas Pieber
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development