[bisq-network/bisq] Suppress netty.shaded debug stack traces in cli (#4091)

[Stan]

Configure cli loggers to avoid scary but ignorable netty debug
log messages with stack traces:  "Reflective setAccessible(true)",
and those showing unsuccessful netty native lib load attempts.
It may be preferable to not use logback in cli, and achieve the
same result programmatically with slf4j, but this shows how to
hide this ugly log output in the meantime.

Remove comment about why these messages were logged, and switch
to non-deprecated ManagedChannelBuilder.forAddress(host, port)
		.usePlaintext().build()
in BisqCliMain.

You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/4091

-- Commit Summary --

  * Suppress netty.shaded debug stack traces in cli

-- File Changes --

    M cli/src/main/java/bisq/cli/app/BisqCliMain.java (6)
    A cli/src/main/resources/logback.xml (17)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/4091.patch
https://github.com/bisq-network/bisq/pull/4091.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/4091
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200323/9f0fd1ad/attachment.html>