I encourage you to create your own project. Alternatively, you could contribute
your code to the logback. Assuming the following conditions:
0) you intend to maintain it
1) you don't mind other logback developers rummaging through and refactoring
your code :-)
2) you agree to the terms of the "Contributor License Agreement" [1]
As for jabsorb.org, I've added it to the list.
[1] http://logback.qos.ch/cla.txt
Arthur Blake wrote:
Ceki said:
>Perhaps the cleanest solution is to trigger reloading of the config file
>manually via some convenient (graphical?) user interface.
I wrote a really nice ajax based graphical UI for log4j recently for a
client that does all that.
It worked out so well, I've been toying of the idea of making an open
source one for logback.
I prefer logback for my own open source projects. If there is
significant interest in this I might consider doing this and either
contributing to logback or open sourcing it on my own...
PS. Ceki, I have yet another open source library that is now dependent
on SLF4J (see http://jabsorb.org) - nice if you could add that to the
main SLF4J page.
Cheers
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
Logback-user mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-user
