[
https://issues.apache.org/jira/browse/FLINK-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023178#comment-17023178
]
Chesnay Schepler commented on FLINK-15756:
------------------------------------------
I can see this working for production deployments but I'm not sure how feasible
this is for testing.
Surely for tests you need more than just {{flink-statefun-sdk}}, at which point
you _will_ have some provided 2.11 dependencies on the test classpath. 2.12
users would then have to override every single dependency to ensure they don't
run into weird incompatibilities.
> 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
> 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)
