GitHub user mcfongtw opened a pull request: https://github.com/apache/flink/pull/4545
[FLINK-6805] [Cassandra-Connector] Shade indirect netty4 dep in pom.xml ## Brief change log - To relocate various *indirect* netty4 dep of ver 4.0.33.Final to classpath of Flink's flavor using Maven shade plugin. ## Verifying this change - Passed local `mvn clean verify` as well as TravisCI tests ## What is the purpose of the change - Shade *(indirect)* netty4 dependencies to avoid class clash in the future. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / no) **slightly related**, shade a netty4 dep. - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / no) no - The serializers: (yes / no / don't know) no - The runtime per-record code paths (performance sensitive): (yes / no / don't know) no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know) no ## Documentation - Does this pull request introduce a new feature? (yes / no) no - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) N.A. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mcfongtw/flink FLINK-6805 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/4545.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 #4545 ---- commit f852eccd24b44ceece6e74bc06c24a77a9acb151 Author: Michael Fong <mcfong.o...@gmail.com> Date: 2017-08-15T06:22:23Z [FLINK-6805] [Cassandra-Connector] Shade indirect netty4 dep To relocate various *indirect* netty4 dep of ver 4.0.33.Final to classpath of Flink flavor using Maven shade plugin. ---- --- 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. ---