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
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.
Related
I am working on adding a proxy for Github Hosted maven repo. I have created the proxy and gave the remote storage url value as github url.
Anyone aware of how we can set up credentials for Nexus repo manager to talk to Github Repo. I am new to this stuff, so any help would be highly appreciated. I am guessing we might need to setup some generic user in github and created authentication token and use those for nexus to talk to Github?
Thanks in advance.
So I currently am trying to get artifacts from repo.osegeo.org, which is a Nexus V3. I am having issues getting the artifacts to populate into my virtual repo that i created which holds the remote osegeo repo, libs release, libs snapshot and also my local repos. I have tried following the work around that is stated in this link below:
https://community.sonatype.com/t/maven-nexus-v3-remote-repository-integration-with-artifactory/2149
But I still have trouble actually getting the artifacts in my repo. Any ideas on what to do?
I suggest checking the following:
Connectivity - Is Artifactory able to reach the Nexus repository and vice versa?
The URL which is configured and if it is configured correctly.
Enable Bypass HEAD requests on the remote repository - Nexus can block HEAD requests and by default, Artifactory will create HEAD requests first before the GET requests to check if the artifact exists before attempting to resolve it.
If the Nexus repository requires authentication - Do not forget to put username and password under the advanced tab.
If there is also a reverse proxy in front of Nexus, you can try to bypass it and check if this works, if it does, the problem is probably the RP.
Check if the Maven client is configured correctly to work against the virtual repository (You didn't mention if you are able to publish or fetch from the local repository).
I am new to nexus and have installed my nexus manager on Linux box. I have added the remote proxy certificate from the Repositories->Settings page and have also setup the proxy settings, but still I am gettin gthe status in the repositories list as Online - Remote Connection Pending Is there anything else I need to do to access the remote maven-central repository?
Current Nexus 3 builds don't do the automatic connection test that Nexus 2 does. The status will change to online when the first outbound request is made to central. Try running a build against the server, that should do it.
If it doesn't, then you have a network problem, check the logs for details.
I work with an external company on a large project with hundreds of their own artifacts and plugins. Every developer can download them from remote repository only with per-user personal VPN.
I want to set up an intranet Nexus repository that mirrors remote repository for use with Jenkins. Problem is that there is no chance to have a VPN account for Nexus (neither Jenkins). So while every developer has these artifacts in a local repository, we need to manually update Jenkins' m2 repostiory, which is troublesome.
We've came to few ideas, bot none of these sound great:
Manually rsync my local repository to Jenkins' local repository
Mount Jenkins' local repository with sshfs to my .m2/repository so it gets updated on builds I do (so I don't have a real local repository on my disk, it's mounted)
Set up Nexus, create a user nexus on my machine and let him use my VPN connection as a proxy to remote repository (it creates a loop: my maven - Nexus - my VPN - remote)
How would you recommend to set up Nexus for Jenkins in that situation?
Ultimately you would save the external company a lot of traffic and money if you can proxy their Nexus repo with your own Nexus repo. This should provide enough reasons to set up a VPN user for Nexus. It can be very limited and have only access to the Nexus instance there and even be secured with a specific account in Nexus as well.
Every other workaround will ultimately be a hack. Worst case I would set up Nexus in your company and get it to access the external network with your user account, but a reasonable organization would understand the benefits of setting this up properly.
And if you are both using Nexus Professional you could use Smart Proxy for even better trusted connections and immediate updates of available components.
Intelliji Idea shiped with 3 free online repository in settings -> maven -> artifactory or nexus service url
http://oss.sonatype.org/service/local/
http://repo.jfrog.org/artifactory/api/
https://repository.jboss.org/nexus/service/local/
all this repos are unavialable (404 error or password protected).
Can you give more free artifactory or nexus service url without password protect?
IDEA has no settings for password on repo URL.
The service URLs are used for attaching remote libraries to a module by running class search queries using the REST APIs available at those URLs and downloading the found librarie from the remote Artifactory.
The REST URLs aren't meant to be directly browsable.
Maybe this explains it better: http://blogs.jetbrains.com/idea/2010/08/getting-external-libraries-easily/
IDEA uses the REST services to get listings of all the repositories available on each host. All three work for me on my machine which is on a network without an HTTP proxy. Is it possible you are on a network with a proxy?
Those urls appear to be pointed at the REST resources of each system, they aren't repositories, not sure what the intellij guys were attempting to do.
If you need a repo to host your own stuff in for free, see here: http://nexus.sonatype.org/oss-repository-hosting.html
If you are trying to access the repositories on Nexus, then you can find them by browsing http://oss.sonatype.org or https://repository.jboss.org/nexus/
Sonatype's service URL now only supports https, so if you're not finding expected artifacts, try updating your Intellij Idea Maven > Repositories setting to https://oss.sonatype.org/service/local/