Am I mistaken to think that a
<mirrors>
<mirror>
<!--This sends everything else to /public -->
<id>nexus</id>
<mirrorOf>*</mirrorOf>
<url>http://myRepoURL:8081/nexus/content/groups/public</url>
</mirror>
</mirrors>
in my settings.xml will stop Maven from reaching a repo that someone
defined in a jar that I include as a dependency?
I believe that this setting sucks up any attempt by Maven on the
developers workstation to reach any repo and forces it to mine.
I will defer to your superior knowledge of Maven and repos but this was
the belief that triggered my comments about the benefit of a properly
configured Maven and repo preventing the problem in this case.
Am I wrong in thinking that I am safe from third party libraries
interfering with my master plan of library reference?
Ron
On 04/07/2012 4:36 PM, Wayne Fay wrote:
This whole problem would not even be in the forum if a repo had been
installed.
Well, Josef did say in another post:
we have a corporate repository acting as a proxy to central !
...
But bad luck, our repository is really just a mirror of central and
contains the same rubbish for xalan-2.7.1.pom and jar
So it seems he does have some kind of a corporate repository which is
acting as a proxy. I don't know any more details though (what MRM he
is running, what version, how it is configured, etc) which might be
helpful to know.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
