[
https://issues.apache.org/jira/browse/FLINK-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512657#comment-15512657
]
ASF GitHub Bot commented on FLINK-4561:
---------------------------------------
Github user shijinkui commented on the issue:
https://github.com/apache/flink/pull/2459
hi, @StephanEwen I have an idea in mind, If there are to much tricky bugs,
and follow "don't change it unless it is broken", after two years can you image
the code like? Full of tricky bugs fix.
I think we should make the code robust, reasonable and readable.
Can we make a long plan with many sub-tasks to reach the above purpose?
Such as reduce the unnecessary module, pom more simple and easy maintain
the pom.xml
Many people consider the Flink code confused and then give up Flink. I
think Flink's features in whole are better, the detail of project need enhance.
How do you think about that?
> replace all the scala version as a `scala.binary.version` property
> ------------------------------------------------------------------
>
> Key: FLINK-4561
> URL: https://issues.apache.org/jira/browse/FLINK-4561
> Project: Flink
> Issue Type: Improvement
> Reporter: shijinkui
>
> replace all the scala version(2.10) as a property `scala.binary.version`
> defined in root pom properties. default scala version property is 2.10.
> modify:
> 1. dependency include scala version
> 2. module defining include scala version
> 3. scala version upgrade to 2.11.8 from 2.11.7
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
