flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7672) Publish Kinesis connector to Maven Central?
Date Fri, 22 Sep 2017 21:54:00 GMT

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

Fabian Hueske commented on FLINK-7672:

AFAIK, calling the API might be considered as linking but I'm not a layer. 
Have you seen other Apache projects publishing Kinesis connector artifacts?

> Publish Kinesis connector to Maven Central?
> -------------------------------------------
>                 Key: FLINK-7672
>                 URL: https://issues.apache.org/jira/browse/FLINK-7672
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Radoslaw Gruchalski
> Hi there, just started working with Flink, second time in the last couple of years. Second
time I hit a major roadblock - the connector I try to work with is not available off the shelf.
I wonder, what's the reason for this connector: https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kinesis/pom.xml
not being Maven Central? It's 21st century, why should I install the jar manually on every
machine where I need to work with the code? Off the top of my head, my local box, jenkins,
customer's deployment. Really?
> I do understand this is coming across rather rude, but come on. There's awesome org.apache.flink
organization on Central, so why not every connector in there?

This message was sent by Atlassian JIRA

View raw message