You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/12/19 16:40:58 UTC

[jira] [Created] (FLINK-5369) jsr305 and logging dependencies should be 'provided' by default

Stephan Ewen created FLINK-5369:
-----------------------------------

             Summary: jsr305 and logging dependencies should be 'provided' by default
                 Key: FLINK-5369
                 URL: https://issues.apache.org/jira/browse/FLINK-5369
             Project: Flink
          Issue Type: Bug
          Components: Build System
            Reporter: Stephan Ewen
            Assignee: Stephan Ewen
             Fix For: 1.2.0


Currently, every project in Flink has a hard (compile scope) dependency on the {{jsr305}}, {{slf4j}}, {{log4j}}, and {{commons-land3}} artifacts, because these dependencies are declared in the root pom.xml. That way they are pulled into every fat jar, including user fat jars as soon as they refer to a connector or library.
    
We should set jsr305, slf4j, log4j, etc to *provided* in the root pom file. That means every project can refer to those classes, but should never re-bundle them (instead assume they are present already). That is achieved by adding them only to the *flink-core* project as actual (compile scope) dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)