You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/01/17 11:08: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=17017915#comment-17017915 ] 

Chesnay Schepler commented on FLINK-12040:
------------------------------------------

1.8: 7fe7417a6ae2969ac5492a291a66b44735a941d5

> 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: Zili Chen
>            Assignee: Zili Chen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.4, 1.9.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)