log4j configuration is being supplied with the library about simple-java-mail HOT 3 CLOSED

Ok, so would you agree that it is harmless to provide logj properties or xml if it targets specific library packages? Because I was actually considering packaging 'sensible' default configurations for all major logging implementations and then let users override it with their own configuration.

What do you think?

from simple-java-mail.

I think the idea with libraries is generally that they can leverage slf4j or some other logging facade so that they don't need to provide any other logging dependencies.

The user of the library just includes the correct slf4j connector and configure their own logging as they need. If they need special logging levels from a library, they can just enable that in their local configuration file by enabling them for the package path for the classes in that library.

Sample log configurations could be provided, but I don't think that most people would use them. I definitely don't think they should be included in the standard packaging of the library.

A little bit of stackoverflow wisdom on this issue:

https://stackoverflow.com/questions/31138140/should-i-put-log4j-properties-file-into-library

http://stackoverflow.com/a/5081386/622115 (check the comments).

from simple-java-mail.

Agreed. I'll exclude the config files from the distributions.

I made everything related to logging test-scoped.

from simple-java-mail.