I've finished a rough prototype of the maven-proxy that I mentioned on IRC last week.
The gist of the concept is this: A common in house repo is good. Although, unless you're mirroring from ibiblio, it is liable to get out of date quickly enough. The maven-proxy solves this by sitting on your intranet server and mimicing ibiblio. All devs are pointed at the intranet server (eg
maven.repo.remote=http://<intranet>:4321 ) When it receives a request, it retrieves from cache / downloads from it's upstream server(s). SNAPSHOT expiration can be faked with a cron job for the time being.
Some halfbaked wiki info - http://wiki.codehaus.org/maven/MavenProxy The binary download is available via the wiki.
It is checked into the codehaus cvs at the moment - host: cvs.codehaus.org cvsroot: /home/cvspublic module: maven-proxy (core / standalone / testrepo)
Issues can be logged into the proxy component on jira Suggestions for features can go into the wiki / jira.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
