Hi,
> The only detail is that in that specific case, we are actually talking
> about the CLI tool: we don't really expect a use to choose the logging
> library for his CLI.
>
> And the error is about providing none.
>
> We can just include a Noop implementation to shut down the warning IMO.
>
> --
Hi Eugen,
On Mon, 2020-06-15 at 11:13 +0300, Eugen Stan wrote:
> Hi,
>
> Removing the implementation leak a MUST.
>
> As I've mentioned in the issue/mail, logging implementation is a
> deployment decision.
I agree
> We should provide documentation and make it easy for people to
> switch.
> In
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
>> 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!
signature.asc
Description: Message
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...
Cheers,
Benoit
Le 13/06/2020 à 20:18, David Leangen a écrit :
>
> Hi!
>
> For the documentation, I have been trying to run t
Hi!
For the documentation, I have been trying to run the “Local” server [1].
[1] https://james.leangen.net/main/3.5/servers/index.html#local
When attempting to use the CLI, I encounter this warning:
```
listDomains
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Default
