You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/01/24 18:14:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17023153#comment-17023153 ] 

Stephan Ewen commented on FLINK-15756:
--------------------------------------

Would be nice to keep Scala out of this as a whole.

StateFun does not use Scala and thinks of Flink as "provided scope". We could say that we depend on a specific Flink Scala version. Users can always use at runtime whichever Fink Scala version they want, it should work.


> 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-0.1
>            Reporter: Chesnay Schepler
>            Priority: Major
>
> 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)