downgrade logging from INFO to DEBUG or TRACE

[whoschek]

Thanks for such a handy library - very useful!

The default log level in logging libs such as logback and log4j is INFO. This implies that by default the logger.info() calls in ConfigurationObjectFactory generate tons of distracting log messages on output. It seems to me folks only want to see those message only in debug or trace mode, and not by default. Having to switch this off manually (ala opt out) seems counter intuitive to me.

[hgschmie]

Choosing INFO was a conscious choice because it ensures that the information required for debugging a problem usually was caught in the log file. Not logging the config settings makes post mortem debugging harder.

[whoschek]

I think that's what the DEBUG level is intended for, conceptually. If all third party libs would log.info() in debug related places there'd be a sea of distractions in everyone's log files.

Anyway, I can manually work around it. Just thought I'd mention it.

[cowtowncoder]

I don't think standard processing should cause any logging: if and when configuration values are to be called, calling application should request those to be logged in my opinion, not just expect them to be produced by side effect. If there are any errors, failures or possible conflicts, those are different matter.

Although I guess I can see the optional need to trace through assignment process wrt defaults, beyond ability to list final results.

[brianm]

While I agree that standard processing should not be noisy, particularly from libraries, I have needed the config output on occasions :-/