[
https://issues.apache.org/jira/browse/FLINK-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15745338#comment-15745338
]
ASF GitHub Bot commented on FLINK-4861:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2664
@StephanEwen @rmetzger, as I revisit this, I'm still questioning the
viability of shading an uber jar. For example, a user depending on a Kafka
connector. Normally the dependency would be packaged in the user's uber jar.
Instead, the user could mark the dependency as provided and copy the connector
jar into `lib/`. If the user makes use of any transitive dependencies (as I
assume Kafka class would be used) then because of the shading would not the
user be required to add Kafka as a dependency to their pom?
> Package optional project artifacts
> ----------------------------------
>
> Key: FLINK-4861
> URL: https://issues.apache.org/jira/browse/FLINK-4861
> Project: Flink
> Issue Type: New Feature
> Components: Build System
> Affects Versions: 1.2.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Fix For: 1.2.0
>
>
> Per the mailing list
> [discussion|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Additional-project-downloads-td13223.html],
> package the Flink libraries and connectors into subdirectories of a new
> {{opt}} directory in the release/snapshot tarballs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
