+1 for slf4j There logging API is way nicer to work with on our end. The setup from a users perspective is nice in that they just drop in the "impl" they want to use. No classpath magic...
On Mon, Jul 7, 2008 at 10:22 AM, Matthew Kemp <[EMAIL PROTECTED]> wrote: > We might want to look at using something like slf4j as the logging API. This > would allow the users to choose their logging framework instead of forcing > them to use log4j. It currently supports logback, x4juli, log4j and JDK > logging. > > http://www.slf4j.org/ > > Matt > > _______________________________________________ > Mailing list: https://launchpad.net/~erma-core > Post to : erma-core@lists.launchpad.net > Unsubscribe : https://launchpad.net/~erma-core > More help : https://help.launchpad.net/ListHelp > > _______________________________________________ Mailing list: https://launchpad.net/~erma-core Post to : erma-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~erma-core More help : https://help.launchpad.net/ListHelp
