GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/1683

    [FLINK-3460] [build] Set Flink dependencies in flink-streaming-connectors 
to provided

    The flink-streaming-connectors all depend on flink-streaming-java in 
compile scope.
    This entails that this dependency is always pulled in, when you build a fat 
jar. By
    setting this dependency to provided, this will be avoided. Furthermore, the 
connectors
    are always used in conjunction with flink-streaming-java. This means that 
you will
    always have an explicit dependency import of flink-streaming-java in your 
build script.
    This allows you to run your program locally but it is also easy to exclude 
the dependency
    from being included in the fat jar by setting it to provided, as well.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink providedDeps

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1683.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1683
    
----
commit fdfc046d5d349afc395cd09a682365b6746aedb3
Author: Till Rohrmann <trohrm...@apache.org>
Date:   2016-02-18T10:23:05Z

    [FLINK-3460] [build] Set Flink dependencies in flink-streaming-connectors 
to provided
    
    The flink-streaming-connectors all depend on flink-streaming-java in 
compile scope.
    This entails that this dependency is always pulled in, when you build a fat 
jar. By
    setting this dependency to provided, this will be avoided. Furthermore, the 
connectors
    are always used in conjunction with flink-streaming-java. This means that 
you will
    always have an explicit dependency import of flink-streaming-java in your 
build script.
    This allows you to run your program locally but it is also easy to exclude 
the dependency
    from being included in the fat jar by setting it to provided, as well.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to