[
https://issues.apache.org/jira/browse/KARAF-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152599#comment-13152599
]
Glen Mazza commented on KARAF-1014:
-----------------------------------
This seems dangerous to do. If a user explicitly specified a file that will
provide some security rules or other important configuration information, but
accidentally mistyped the filename in the ${includes}, then Karaf would run
without the intended security rules or other configuration occurring *and*
quite possibly without the Karaf administrator being aware of that fact. Nine
times out of ten, the would-be Karaf user would be thrilled that Karaf refused
to start, and would then fix the problem--moving the proper config file to the
directory, removing the config file from the ${includes} property, or fixing
the typo over the filename.
> Make files specified by ${includes} optional
> --------------------------------------------
>
> Key: KARAF-1014
> URL: https://issues.apache.org/jira/browse/KARAF-1014
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Affects Versions: 2.2.4
> Reporter: Bengt Rodehav
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> The ${includes} property in custom.properties is used to list property files
> that will be read and evaluated by Karaf at startup. However, if a file
> listed this way does not exist, then Karaf fails to start. When using this as
> a means to give a user the possibility to add custom properties, it makes
> sense to change this behaviour so that Karaf picks up the file if it exists
> otherwise it will be ignored and Karaf will continue its startup process.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
