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 Tue, 22 Nov 2016 19:22:58 GMT

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

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

Github user rmetzger commented on the issue:

    https://github.com/apache/flink/pull/2664
  
    Thank you for fixing the issue so quickly.
    I'm wondering whether the current approach is a good idea, because it requires manual
checking of all transitive dependencies. We have something similar (=manual as well) in the
quickstart, where we exclude some artifact, and it doesn't really happen that people update
that list of excludes.
    So I fear that if somebody changes a connector for example, it will not be added here.
    I guess adding an assembly descriptor for each connector / module would solve the problem
with the transitive dependencies. I don't know if there's a more efficient approach.
    
    What do you think?


> 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