> Hi Mike,
> Logging was overhauled in for 1.0.0, so some of the issues you've raised
> are legacy concerns. Here are my thoughts:
>> The logging backend/configuration happens in the end product.
>> Thus, class JavaDoc should be altered and both get*File methods should
>> be deleted. (Not mentioning that there is no logging.properties anymore)
> This is an oversight from the conversion to SLF4J. I'll remove the
> unused legacy code today - thanks for catching that.
I would even remove the getLogConfigFile() method for two reasons:
1. As I said before, logging happens in the end product
2. This resource won't change anyway. It is safe to include the string
/WEB-INF/classes/logback.xml directly into the resource bundle property
No need for file.separator, we're on a VFS using always a slash.
>> I would replace the file appender with a console appender
> This makes perfect sense, although I'd like to make sure that there are
> also comments in the logback.xml file instructing users how to customize
> the logging configuration - for example, a commented-out sample file
> Your suggestions make sense, so please go ahead and make any changes
> that you see as necessary. Since these are fairly minor feel free to
> commit directly to trunk if you'd like.
I'll have three appenders: jamwiki-stdout, jamwiki-dailyfile,
Only stdout will be active by default.