This is exactly what I want to do but can't figure out an easy way to do
it.
1) To disable central, you need to add this to your .m2/settings.xml:
<settings>
<mirrors>
<mirror>
<mirrorOf>central</mirrorOf>
<url>http://repohost/repodir</url>
<id>internalrepo</id>
</mirror>
</mirrors>
...
It will now always use your repohost instead of central.
2) A local repo cannot be used as a remote repo. This is the problem I
am struggling with because the maven-metadata.xml files do not exist.
If anyone knows of a way to build this metadata from scratch, please
please please reply!
mike
-----Original Message-----
From: Morgan Rachell [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 27, 2006 12:30 PM
To: [email protected]
Subject: M2 still downloads plugins from repo1.maven.org even with
internal plugin repository
Sorry if this seems like a basic config issue (I'm still new to M2), but
I couldn't find an answer searching through the mail list archives.
I'd like to setup an internal plugin repository (actually on our
network). So I ran all mvn commands that I thought users may run ("mvn
ear:ear", "mvn test", etc.) to download all required plugins. I then
copied my local cached repository from C:\Documents and
Settings\mrachell\.m2\repository to the server location
//myserver/projects/maven2repo. Then I updated my pom.xml to point to
the network repo, deleted my local cached repo and re-ran the mvn
commands. Although it is getting most plugins from the internal repo
(the download shows file://... instead of http://...) it is still
downloading some plugins from the internet even though they exist on the
configured internal repo. For example, the following shows that the
first plugin is from the internet, but the next one is from the internal
repo:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
