Following the usual convention for libraries not to dictate the logger configuration, the logback.xml file should be removed from the jar file produced for this library.
This causes an issue where an application will get different logger configuration, depending on the order it happened to discover the jar files.
Though it is possible to work around this by trumping the file with a system property, it would be nice to remove the risk by just removing the file.
Following the usual convention for libraries not to dictate the logger configuration, the logback.xml file should be removed from the jar file produced for this library.
This causes an issue where an application will get different logger configuration, depending on the order it happened to discover the jar files.
Though it is possible to work around this by trumping the file with a system property, it would be nice to remove the risk by just removing the file.