Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
0.9.19
-
None
Description
I'm interested in writing a module for logback to allow on the fly changes to the logger tree - changing levels, adding appenders, maybe adding filters with code supplied dynamically. My vision for the gui is to show the logger tree like a folder tree.
However, now I come to look at it it seems neither the child loggers nor the parent logger of a logger are exposed, which rather blows this whole concept out of the water.
Is there a particularly strong reason for this? If not, I've forked logback here:
http://github.com/Mahoney/logback
and exposed the data. As part of the same thing I changed the children from a List to a Set as it seems more semantically correct and cleans up the code slightly.