Github user aalexandrov commented on the pull request:
https://github.com/apache/flink/pull/880#issuecomment-118066010
OK thanks for the remark.
Although somewhat verbose, this solves my concrete issue. I wonder if the
list can be exclusive, e.g.
```xml
<!-- use Tweet input format -->
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-tweet-inputformat</artifactId>
<version>${project.version}</version>
</dependency>
```
However, it still leaves the question what policy to use for flink-* based
dependencies.
As an example, if I want to include `flink-streaming-contrib` in a module
that is build as a "thin" jar, transitive `flink-*` dependencies that will be
packaged in the `flink-dist` fat jar do not need to be included.
I therefore suggest to at least make this consistent [with the quickstart
poms](https://github.com/apache/flink/blob/master/flink-quickstart/flink-quickstart-java/src/main/resources/archetype-resources/pom.xml)
and [optionally set the scope of already included dependencies to `provided`
if the `build-jar` profile is
activated](https://github.com/apache/flink/blob/master/flink-quickstart/flink-quickstart-java/src/main/resources/archetype-resources/pom.xml#L317).
---
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.
---
