You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/04/26 10:33:00 UTC
[jira] [Commented] (FLINK-12040) Remove unused akka dependencies in
pom.xml
[ https://issues.apache.org/jira/browse/FLINK-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826865#comment-16826865 ]
Till Rohrmann commented on FLINK-12040:
---------------------------------------
If Akka is no longer needed by a module, then let's remove it from it.
> Remove unused akka dependencies in pom.xml
> ------------------------------------------
>
> Key: FLINK-12040
> URL: https://issues.apache.org/jira/browse/FLINK-12040
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 1.9.0
> Reporter: TisonKun
> Assignee: TisonKun
> Priority: Major
> Fix For: 1.9.0
>
>
> With FLIP-6 and FLINK-10392 we can remove several now unused dependencies in pom.xml such as {{flink-yarn-tests}} and {{flink-client}} (if FLINK-11146 get resolved).
> Ideally it should be only {{flink-runtime}} has this dependency and thus we can make a relocation for users to use their own akka. Otherwise we might run into the situation that Spark once meet. One of the most challenging part is {{flink-mesos}} still heavily rely on direct access to akka.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)