karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Lange (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-4700) Overrides and blacklist do not work by default and produce an exception
Date Tue, 06 Sep 2016 14:23:20 GMT
Fabian Lange created KARAF-4700:

             Summary: Overrides and blacklist do not work by default and produce an exception
                 Key: KARAF-4700
                 URL: https://issues.apache.org/jira/browse/KARAF-4700
             Project: Karaf
          Issue Type: Bug
            Reporter: Fabian Lange

The FeaturesServiceImpl supports overrides and blacklist.
They are configured in the Activator:

If not configured they will default to a file which is not existing in the distribution by
        String overrides = getString("overrides", new File(System.getProperty("karaf.etc"),
        String blacklisted = getString("blacklisted", new File(System.getProperty("karaf.etc"),

This causes Exceptions later down the line, e.g. here: 

The code is guarded with a null check, so there has been a possibility not to use the blacklist
or override feature at all by providing them as "null".
but the way these properties are read, they never can be null, they either refer to a file
the user configured or to the default file.

It would be great if it would be possible to turn the feature off some how.

the best workaround right now is to add empty files, which will at least prevent the file
not found exception, but it is still unnecessary file io (which admittedly is a minor concern)

This message was sent by Atlassian JIRA

View raw message