flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-12040) Remove unused akka dependencies in pom.xml
Date Sat, 27 Apr 2019 07:17:00 GMT

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

Chesnay Schepler closed FLINK-12040.
------------------------------------
    Resolution: Fixed

master: ceec2360d6492f44467f47c93b17a9b20cbe9715

> 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
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  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
(v7.6.3#76005)

Mime
View raw message