I need to use the Confluent kafka-avro-serializer
Maven artifact. From the official guide I should add this repository to my Maven pom
<repository>
<id>confluent</id>
<url>http://packages.confluent.io/maven/</url>
</repository>
The problem is that the URL http://packages.confluent.io/maven/ seems to not work at the moment as I get the response below
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>maven/</Key>
<RequestId>15E287D11E5D4DFA</RequestId>
<HostId>
QVr9lCF0y3SrQoa1Z0jDWtmxD3eJz1gAEdivauojVJ+Bexb2gB6JsMpnXc+JjF95i082hgSLJSM=
</HostId>
</Error>
In fact Maven does not find the artifact
<dependency>
<groupId>io.confluent</groupId>
<artifactId>kafka-avro-serializer</artifactId>
<version>3.1.1</version>
</dependency>
Do you know what the problem could be? Thank you
You can add a mirror in you maven settings file to fetch the jars from confluent repo along with repository config . Changes needed are Add a mirror in settings.xml
In repository section of maven settings add this
The file is available, since you can download it if you go to it directly: http://packages.confluent.io/maven/io/confluent/kafka-avro-serializer/3.1.1/kafka-avro-serializer-3.1.1.jar
You could try adding the -U flag to your maven command to force download of cached files.
The root of the repo isn't browsable which is why you are getting the message when browsing to http://packages.confluent.io/maven/
Just like you I use a company repository (Sonatype Nexus) and was not able to proxy the confluent's repository.
Then I changed my maven settings.xml to exclude confluent form the mirrored repository:
This way, artifacts resolution works for confluents' artifacts as well.
Not as neat as proxying the repo but at least less cumbersome than downloading and registering each dependency manually.
When trying to connect Artifactory to the Confluent Maven repository you have to set the repo URL in Artifactory to be either
http://packages.confluent.io/maven
orhttps://packages.confluent.io/maven
(both schemes seem to work fine). The confusing part is that when you ask Artifactory to test that URL it will fail with the message "Input may not be null". You are also unable to browse the repository in Artifactory. However, regardless of these problems, artifacts will be downloaded and cached when clients request them.