1

being behind a Nexus Repository Manager (3.4.x) I'm trying to setup a connection to the Confluent repository / Maven. I tried several steps, the most complete instructions I tried can be found here: Confluent Maven repository not working?

My workstation connects to a Nexus Repository Nexus. I have admin privileges on this Nexus.

Remote repository settings -- Nexus (1)

Further settings -- Nexus (2)

Using these settings I cannot connect to the Confluent repository. The Nexus works fine with other third party repositories.

I tried using the health check, but it just leaves me with 'Insufficient trend data' as shown here: Insufficient trend Data -- Nexus (3)

I currently spend 1.5 days on this. I locally embedded some of the needed jars, but for production this is obviously not feasible.

What am I missing here? Is there a way to check availability of third party repositories from Nexus except Health Check? If you already have this setup running, I'm looking forward to your replies.

Manually added:
kafka-avro-serializer, kafka-schema-registry-client
Currently unresolable: common-config

OneCricketeer
  • 179,855
  • 19
  • 132
  • 245
nykon
  • 504
  • 4
  • 18
  • I would check the remote repository http://packages.confluent.io/maven/ ? Which looks like not working ? Moved ...needing authorization etc. ? – khmarbaise Jun 14 '18 at 13:45
  • It's the offical repository URL, reference: https://docs.confluent.io/3.0.0/installation.html#installation-maven – nykon Jun 14 '18 at 13:54

1 Answers1

1

It looks like the URL you're pointing to packages.confluent.io/maven is returning a 404.

My guess is that this is causing Nexus to think that the downstream repository isn't working properly.

I'd contact the people who operate the confluent server and let them know the configuration in the documentation isn't working properly.

Chris S.
  • 192
  • 3
  • Thank you for your reply - It's the offical repository URL, reference: docs.confluent.io/3.0.0/installation.html#installation-maven. I read about the issue and it just seems to be a browser related issue and the repository therefore working fine – nykon Jun 14 '18 at 14:29
  • I was using CURL to inspect the repository and it was returning 404. If you wanted to test further, you could see if an attempt to retrieve an actual artifact returned 200 rather than 404. – Chris S. Jun 14 '18 at 15:46
  • Please refer to the accepted answer of the linked article https://stackoverflow.com/a/43489639/6500730 'the root repo isn't browseable', which does not seem to impede Maven – nykon Jun 14 '18 at 16:41