You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by StephanEwen <gi...@git.apache.org> on 2018/04/30 19:47:14 UTC

[GitHub] flink issue #5900: [FLINK-9222][docs] add documentation for setting up Gradl...

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.


---