Gustavo Valle wrote:
I believe by doing this you are overriding the default location for the central repository, and forcing maven to look for everything on localhost. This won't work because it will fail to find its plugins there unless youve primed it already. What you want, from what you've described is a web app that will act as a caching Maven repository. Maven won't do this itself. If you override the central repository then the override location(s) are the only places maven will look for artifacts. The solution is Maven Proxy from codehaus. When you request an artifact from Maven Proxy, it looks at a local (to it) repository and serves it from there, or if it can't, goes to an actual remote repository to fetch it. Sadly, the site is down currently, and likely till the end of the week. The google cache of the main page is here: http://66.102.7.104/search?q=cache:zfDNHXmX7sIJ:maven-proxy.codehaus.org/+maven+proxy+site:codehaus.org&hl=en&lr=&client=firefox-a&strip=1<repositories> <repository> <id>central</id> <url>http://localhost:8080/maven</url> </repository> </repositories><pluginRepositories> <pluginRepository> <id>central</id> <url>http://localhost:8080/maven</url> </pluginRepository> </pluginRepositories>
Personally I recommend using an installed copy of Maven Proxy as a mirror for central (specified either in your POM or your settings.xml) and using a seperate internal repository for internally developed projects.
Brad --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
