Why not have your repo proxy the extra ones so everyone's settings.xml
points to your repo and its is up to the repo manager to set up the
permitted repo.
Ron
On 08/05/2015 2:39 PM, Rick R wrote:
I'm trying to figure out why Maven is choosing a 3rd party repo defined in
my settings xml
I'm trying to figure out why Maven is choosing a 3rd party repo defined in
my settings xml BEFORE trying to search in our internal Nexus repo.
My settings xml has the following profile which is set as the active one.
profile
idncs-main/id
repositories
repository
I mention that at the end of the above email... for some reason I'm having
trouble proxing this one ZK repository that requires a username and
password (which I've added in the nexus auth settings.) I think the error
Nexus mentioned was remote access not allowed or something to that
effect.
On
It actually pulls the correct artifacts from the 3rd party repos just fine
(the one you see called ZK in my settings.) There are a bunch of them in
there and the upgrade them quite frequently so I'd prefer to not have to
manually add them, especially since their repos work just fine.
The annoying
Is it possible that Maven is having the same trouble as Nexus and can
not get into the repo and just moves on to the next one since it has no
idea about which dependency is going to be found in the repo and maybe
the next one will work better and get it everything that it needs.
It would not
