[SOLVED] Maven Could Not Find Artifact io.confluent:kafka-avro-serializer:jar:3.3.1 In Central (https://repo.maven.apache.org/maven2) – Trivial Reason And Easy Solution In 1 Min!

[ERROR] Maven Could not find artifact io.confluent:kafka-avro-serializer:jar:3.3.1 in central (https://repo.maven.apache.org/maven2) - trvial reason and easy solution in 1 min!
Photo by Árpád Czapp on Unsplash
Share this post and Earn Free Points!

It looks like you are trying to use the io.confluent:kafka-avro-serializer library in your Maven" project, but Maven" is unable to find the artifact.


Confluent Kafka

Apache Kafka" is a distributed streaming platform that is used to build real-time data pipelines and streaming applications. It is designed to handle high volumes of data and enable real-time data processing.

Confluent is a company that was founded by the creators of Kafka and provides a commercial distribution of Kafka as well as a streaming platform built on top of Kafka". Confluent’s platform includes additional tools and features for managing and deploying Kafka clusters, as well as connectors for integrating Kafka with other systems.

Some of the key features of Kafka include:

  • Publish-subscribe messaging: Kafka allows producers to send data to topics, and consumers to subscribe to and read from those topics.
  • Scalability: Kafka is designed to handle high throughput and can scale horizontally by adding more brokers to a cluster.
  • Durability: Kafka stores data in a distributed manner across multiple brokers, which ensures that data is not lost even if a broker fails.
  • Low latency: Kafka is designed to have low latency and is suitable for real-time data processing applications.

Confluent Schema Registry

The Confluent Schema Registry is a central repository for storing and managing Avro" schemas. It is part of the Confluent" Platform, which is a commercial distribution of Apache Kafka" that includes additional tools and features for managing and deploying Kafka clusters.

The Schema Registry provides several benefits for applications that use Kafka and Avro":

  • It allows you to store and retrieve Avro" schemas, which makes it easier to manage the schemas used by your applications.
  • It provides versioning and evolution support for Avro" schemas, which allows you to make changes to a schema while still being able to read data produced with an older version of the schema.
  • It provides compatibility checks to ensure that new versions of a schema are compatible with previous versions. This helps to prevent data loss or corruption when upgrading to a new version of a schema.

To use the Confluent Schema Registry, you will need to add the kafka-avro-serializer library to your application’s dependencies and configure it to use the Schema Registry. You can then use the KafkaAvroSerializer and KafkaAvroDeserializer classes to serialize and deserialize Avro" data to and from Kafka topics.

I hope this helps! Let me know if you have any other questions about Kafka or Confluent.

Cause of Maven Could Not Find Artifact

This is typical error [ Maven" could not find artifact ] when you first time use dependencies which are not coming from the most popular Maven" repository. In this case I wanted to use package which is coming from Confluent Maven repository.

There are a few possible reasons for this:

  1. The artifact may not exist in the Maven" repository that you are using. Make sure that you have the correct groupId, artifactId, and version for the artifact, and check that it is available in the repository.
  2. The dependency may not be declared in your project’s pom.xml file.
  1. You may not have internet access, or the Maven" repository may be down. In this case, you can try again later, or you can try using a different repository.
  2. There may be a problem with your Maven" installation. In this case, you can try deleting your local repository (located in the .m2 directory) and running mvn clean install again. This will force Maven" to download all of the necessary artifacts again.


You need to add missing repository. You can do it in two ways. You need to choose which one is better for you. In first option the repository will be only visible in this particular project. If you will go with second option the new repository will be visible for all your projects – it means that if you will create in the future the another project which requires packages from this repository, it will be able to pull dependencies.

  • adding directly to your project pom.xml file.
  • adding to settings.xml" file

Option #1

Please include this snip of xml" code in your pom.xml file:


Option #2

Put above xml" code in existing profile in setting.xml or create the new one, but:

Remember: if you will create new profile you must remember to add this profile in section <activeProfiles>


I hope this helps! Let me know if you have any other questions about the Confluent Schema Registry, Confluent Kafka and error: Maven" could not find Artifact

Could You Please Share This Post? 
I appreciate It And Thank YOU! :)
Have A Nice Day!

How useful was this post?

Click on a star to rate it!

Average rating 4.9 / 5. Vote count: 2114

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?