You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Ben Clark (JIRA)" <ji...@apache.org> on 2017/11/22 11:22:00 UTC

[jira] [Commented] (KARAF-3949) Be able to load System properties from another file than etc/system.properties

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

Ben Clark commented on KARAF-3949:
----------------------------------

When searching for a way to do this, I found that through KARAF-5440 system.properites in Karaf 4.1.3 contains the line: 

{code:java}
${optionals} = custom.system.properties
{code}

Thought I should mention this as I assume this issue can be closed? 

> Be able to load System properties from another file than etc/system.properties
> ------------------------------------------------------------------------------
>
>                 Key: KARAF-3949
>                 URL: https://issues.apache.org/jira/browse/KARAF-3949
>             Project: Karaf
>          Issue Type: Improvement
>          Components: karaf-core
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> We can use etc/system.properties to define System properties.
> The Karaf Main loads (and may override) System properties from this file.
> When we create a custom distribution, and users want to add their own System properties, they have to provision a complete etc/system.properties.
> It makes sense to be able to provision a etc/systemuser.properties without altering the etc/system.properties: Karaf Main can load the System.properties from both, first from etc/system.properties and after from etc/systemuser.properties (optional).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)