You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/04/28 14:52:04 UTC
[jira] [Updated] (FLINK-6415) Make sure core Flink artifacts have
no specific logger dependency
[ https://issues.apache.org/jira/browse/FLINK-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen updated FLINK-6415:
--------------------------------
Summary: Make sure core Flink artifacts have no specific logger dependency (was: Make sure Flink artifacts have no specific logger dependency)
> Make sure core Flink artifacts have no specific logger dependency
> -----------------------------------------------------------------
>
> Key: FLINK-6415
> URL: https://issues.apache.org/jira/browse/FLINK-6415
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.3.0
>
>
> Flink's code is written against {{slf4j}}
> To make sure users can use their custom logging framework we need to have
> - no direct compile-scope dependency in any core
> - a dependency in {{flink-dist}} that is not in the fat jar
> - an explicit dependency in {{examples}} (to see logs when running in the IDE)
> - an explicit test dependency (for logs of test execution)
> All except point (1) are already fixed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)