The following situation:
We have quite large projects that I'm trying to change. Therefore, we installed our own nexus repository manager. Everything works so far, but now we are faced with a situation where each developer must enter the proxy server username and password in settings.xml to receive artifacts from the outside (i.e. the Internet).
Unfortunately, developers need to change their proxy passwords from time to time, and they need apapt the settings.xml again.
The connection to our connection is not routed through a proxy. Is it possible to configure a similar DNS approach:
- Client A asked (intern company, non-proxy) a link for a.jar artifact.
- It is not in the local repositories, so the link then retrieves this artifact from the maven center and stores it in the local cache.
- Client A receives the a.jar artifact as if it came directly from the company.
- Everyone is happy:)
source share