You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2017/05/15 15:36:04 UTC

[jira] [Closed] (FLINK-2593) Revisit Flink's shading policy

     [ https://issues.apache.org/jira/browse/FLINK-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger closed FLINK-2593.
---------------------------------
    Resolution: Duplicate

Subsumed by FLINK-6529

> Revisit Flink's shading policy
> ------------------------------
>
>                 Key: FLINK-2593
>                 URL: https://issues.apache.org/jira/browse/FLINK-2593
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Till Rohrmann
>            Priority: Minor
>
> At the moment Flink does not follow a consistent shading policy which dictates which dependencies should be shaded away and which to keep. This becomes especially important for utility libraries which are likely to be used by the users as well. By not shading these dependencies, the user is constrained to use exactly the same version in his code. This might cause problems for the user.
> Some of the dependencies which Flink should probably shade away are {{Akka}}, {{Protobuf}} and {{Curator}}, for example.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)