Following situation:
We have a quite big projects that I am trying to mavenize. Therefore we have installed our own nexus repo manager. Everything works so far but now we face the situation that every dev must enter his/her proxy username and password into the
settings.xml
to get artifacts from outside (i.e. Internet).
Unfortunately the devs need to change their proxy passwords every now and then and they need to apapt the settings.xml again.
The connection to our nexus is not routed over the proxy. Is there a possibility to configure a DNS like approach:
- Client A asked (company intern, non-proxy) nexus for artifact a.jar.
- It is not located in the local repos, so the nexus then retrieves that artifact from maven central and stores it in it's local cache.
- Client A gets the artifact a.jar as if it came directly from the company nexus.
- Everybody is happy :)