[
https://issues.apache.org/jira/browse/FLINK-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15749204#comment-15749204
]
ASF GitHub Bot commented on FLINK-4861:
---------------------------------------
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3000
`flink-avro` is included in the distribution.
Will adding a scala suffix to`flink-hcatalog` break API compatibility?
I see now that we can use `combine.self="override"` to allow configuration
defined in the parent pom to be overwritten in child poms.
I am thinking that we need to take a more nuanced approach to copying or
creating jars for `opt/`. What if we scale this initial PR to only include
metrics, cep, ml, and gelly?
> 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)
