You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/01/30 12:09:00 UTC

[jira] [Closed] (FLINK-15756) StateFun poms are inconsistent in their scala version usages

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

Tzu-Li (Gordon) Tai closed FLINK-15756.
---------------------------------------
    Fix Version/s: statefun-1.1
       Resolution: Fixed

Fixed in master via f3b04fa1190ce97199f0243ce19b575d0e7169c2.

> StateFun poms are inconsistent in their scala version usages
> ------------------------------------------------------------
>
>                 Key: FLINK-15756
>                 URL: https://issues.apache.org/jira/browse/FLINK-15756
>             Project: Flink
>          Issue Type: Bug
>          Components: Stateful Functions
>    Affects Versions: statefun-1.1
>            Reporter: Chesnay Schepler
>            Assignee: Igal Shilman
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: statefun-1.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Some statefun modules use hard-coded scala versions (e.g., statefun-flink-core), while others are parameterized (e.g., statefun-flink-harness).
> Either we should change this or document why it works the way it does.
> Naturally it also begs the questions whether the statefun modules also require scala suffixes.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)