Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 28 Aug 2015 14:00:51 +0000 (UTC)
From: "Till Rohrmann (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.12859927.1440770425000.194234.1440770451159@Atlassian.JIRA>
In-Reply-To: <JIRA.12859927.1440770425000@Atlassian.JIRA>
References: <JIRA.12859927.1440770425000@Atlassian.JIRA>
 <JIRA.12859927.1440770425972@arcas>
Subject: [jira] [Created] (FLINK-2593) Revisit Flink's shading policy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Till Rohrmann created FLINK-2593:
------------------------------------

             Summary: Revisit Flink's shading policy
                 Key: FLINK-2593
                 URL: https://issues.apache.org/jira/browse/FLINK-2593
             Project: Flink
          Issue Type: Improvement
            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.4#6332)