Github user zentol commented on the issue:
https://github.com/apache/flink/pull/5303
see https://issues.apache.org/jira/browse/FLINK-8444
---
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5303
Sounds good. Just to be sure: My write-up above was meant as a suggestion
or food-for-thought, not as a final decision ;-)
We should probably bring these thoughts to a dev discussion and
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/5303
In that case I'll revert the commit that caused all this, close this PR and
open a new JIRA for adding a new dependency management section to the project
setup guide (along with a sweep across the doc
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5303
I would suggest to start thinking about the dependencies the following way:
- There are pure user-code projects where the Flink runtime is "provided"
and they are started using an exist
