[
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-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> 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)
