[jira] [Commented] (KARAF-955) Confusing behavior of ConfigAdmin

["Grzegorz Grzybek (JIRA)" <ji...@apache.org>]

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

Grzegorz Grzybek commented on KARAF-955:
----------------------------------------

[~gnt], [~jbonofre] I think it'd be ok to _won't fix_ this issue.

> Confusing behavior of ConfigAdmin
> ---------------------------------
>
>                 Key: KARAF-955
>                 URL: https://issues.apache.org/jira/browse/KARAF-955
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-config
>    Affects Versions: 2.2.4
>            Reporter: Sergey Zhemzhitsky
>
> Hi there,
> I've faced with the following behavior of ConfigAdmin which I suppose is a little bit confusing.
> Steps to reproduce:
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # *karaf.log* file should be there
> # Stop Karaf
> # Go to *$\{karaf.home}/data/log* directory and delete *karaf.log* file
> # When Karaf is stopped change *log4j.appender.out.file* property in the *$\{karaf.home}/etc/org.ops4j.pax.logging.cfg* file from *$\{karaf.data}/log/karaf.log* to *$\{karaf.data}/log/karaf1.log*
> # Start Karaf
> # Go to *$\{karaf.home}/data/log* directory
> # Only *karaf1.log* file is expected to be there, but empty *karaf.log* that has been deleted on the step 4 is also there.



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