You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/09/22 21:43:01 UTC
[jira] [Resolved] (FLINK-7672) Publish Kinesis connector to Maven
Central?
[ https://issues.apache.org/jira/browse/FLINK-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Hueske resolved FLINK-7672.
----------------------------------
Resolution: Unresolved
Unfortunately, Amazon Software License is Cat X (https://www.apache.org/legal/resolved.html#category-x) and cannot be part of distributed artifact.
I know this is annoying but this cannot be resolved from our side.
> 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
(v6.4.14#64029)