[
https://issues.apache.org/jira/browse/FLINK-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608623#comment-15608623
]
ASF GitHub Bot commented on FLINK-4861:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2664
I think this is a good idea.
However, having all the individual dependency jar files in the folder makes
it very hard to use. To actually use the libs (from an IDE without maven) it is
very hard to understand what jar file would belong to which connector.
Would it make sense to have a sub directory for each connector, with its
specific dependencies?
I am also wondering if there are maybe some unwanted test dependencies in
the binary build. For example `opt/connectors/batch/derby-10.4.2.0.jar` is a
test dependency from the JDBC in/out formats.
> 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)
