[
https://issues.apache.org/jira/browse/FLINK-9222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458960#comment-16458960
]
ASF GitHub Bot commented on FLINK-9222:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5900
Nice addition!
A few things I would like to double check on the quickstart configuration
(I am not fluent enough Gradle):
- We do not need to hide/shade any dependencies in the user code. In
Maven, we use the shade plugin, but only to build an uber jar, not to actually
relocate dependencies. Is that the same in the Gradle quickstart?
- The Flink core dependencies need to be in a scope equivalent to
"provided", so they do not end up in the uber jar. Can we do something similar
in Gradle? This has been a frequent source of unnecessarily bloated application
jars.
- The Maven quickstart template uses a trick to make sure that the
provided dependencies are still in the classpath when we run the program in the
IDE: A profile that activates in IDEA (by a property variable) and alters the
scope from *provided* to *compile*. Not sure if that is strictly necessary, but
may be helpful.
> Add a Gradle Quickstart
> -----------------------
>
> Key: FLINK-9222
> URL: https://issues.apache.org/jira/browse/FLINK-9222
> Project: Flink
> Issue Type: Improvement
> Components: Project Website, Quickstarts
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Critical
>
> Having a proper project template helps a lot in getting dependencies right.
> For example, setting the core dependencies to "provided", the connector /
> library dependencies to "compile", etc.
> The Maven quickstarts are in good shape by now, but there is none for Gradle
> and Gradle users to get this wrong quite often.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
