flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4861) Package optional project artifacts
Date Thu, 24 Nov 2016 16:18:59 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15693654#comment-15693654
] 

ASF GitHub Bot commented on FLINK-4861:
---------------------------------------

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/2664
  
    I had the same thought. We could add the maven assembly plugin / shade plugin to each
connector / library to build a fat jar, and then add some logic to flink-dist to collect these
fat jars into the final dist.
    I'm not sure how easy it is to pull build outputs from other modules into the dist module,
but we are doing that for the examples as well.


> 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)

Mime
View raw message