karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (KARAF-2483) Add -p (--persist) option to the log:set command
Date Mon, 23 Dec 2013 13:38:50 GMT

     [ https://issues.apache.org/jira/browse/KARAF-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré resolved KARAF-2483.

    Resolution: Won't Fix

It was a misunderstanding about the DEFAULT level used in log:set.

I documented it, and revert the Felix ConfigAdmin/FileInstall property.

This option doesn't make sense now.

> 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.1, 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
> 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

View raw message