[
https://issues.apache.org/jira/browse/KARAF-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2483:
----------------------------------------
Fix Version/s: (was: 3.1.0)
3.0.0
> Add -p (--persist) option to the log:set command
> ------------------------------------------------
>
> Key: KARAF-2483
> URL: https://issues.apache.org/jira/browse/KARAF-2483
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 3.0.0, 2.3.4
>
>
> In order to be compliant with the documentation, the log:set command doesn't
> update etc/org.ops4j.pax.logging.cfg file anymore (especially to be able to
> use log:set DEFAULT to "reload" the loggers configuration from the file).
> However, some users expect that the log:set command updates the
> etc/org.ops4j.pax.logging.cfg file.
> I propose to add -p (--persist) option to log:set command to store the change
> in the etc/org.ops4j.pax.logging.cfg file and display a warning message
> saying that the DEFAULT "configuration" will be overrided.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
