[
https://issues.apache.org/jira/browse/FLINK-11209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11209:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Provide more complete guidance for the log usage documentation
> --------------------------------------------------------------
>
> Key: FLINK-11209
> URL: https://issues.apache.org/jira/browse/FLINK-11209
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: vinoyang
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> The current documentation does not provide detailed guidance when users
> attempt to use logback as the underlying logging framework. Since Flink only
> contains log4j dependency jars. The documentation says that if you want to
> switch to logback, you only need to exclude the log4j dependency, but it does
> not remind the user to add a dependency on the logback. I hope to add the
> following information:
> * Remove the dependencies of log4j and slf4j-log4j in the lib folder;
> * Where to download the logback-* jar
> * Introduce logback-core/logback-classic/logback-access dependencies
--
This message was sent by Atlassian Jira
(v8.3.4#803005)