Hi, Removing the implementation leak a MUST.
As I've mentioned in the issue/mail, logging implementation is a deployment decision. We should provide documentation and make it easy for people to switch. In a "product like" distribution we will deliver an implementation suitable for that use case. Libraries should NOT depend on an logging implementation. Add the logging implementation to the test scope if needed. == The rationale Some people log to memory Some people log to (rotating) files Some people log to local (on the same host) log aggregator Some people log to a central, over the network logging collector. Every use case is valid - it depends on the decisions made when the infrastructure was built. We can't know in advance what users will use. La 15.06.2020 08:09, David Leangen a scris: >>> When attempting to use the CLI, I encounter this warning: >> Very likely we have 2 logging dependencies on the classpath. >> >> This needs to be rationalised. I will add this to JAMES-3214 as this >> relates to cleaning dependency mess… > > Perfect, thank you! > > -- Eugen Stan +40720 898 747 / netdava.com
<<attachment: eugen_stan.vcf>>
signature.asc
Description: OpenPGP digital signature
