That sounds like a really bad idea to me. Awful. Mirroring the entire maven repository is a pointless waste of your bandwidth and diskspace, and more importantly a waste of the bandwidth of the ASF.
You do not need every copy of every lib going back to the creation of maven itself. And IMO people who try to download that should be banned from accessing the repository at all. Follow Brian's suggestion: set up a maven proxy (such as Nexus), and run your build. Or in your case, sit with your security people and do this from a machine that *does* have internet access. This will cause all the files you need, and *only the files you need* to be downloaded and stored. Then simply run a webserver that points at the files that the maven proxy has downloaded. That webserver will now act as a read-only copy of *just the part of the maven repository that you need*. As was noted, there is not much point in using a maven proxy to serve these read-only files once you've downloaded them the first time. Simon Seth Geoghegan schrieb: > Thanks for the great feedback everyone. I am going to put together a list > of options for management and advocate for mirroring the entire repository. > It will be a tough sell, since they are very cautious about open source > software. However, as Brian mentioned, anything else would be tedious at > best. > > Thanks for the tip Andreas, I hadn't considered using Tomcat as my > controlled repository. I'll look into that. > > Regards, > ~Seth > > > On 5/23/08, Richard Chamberlain <[EMAIL PROTECTED]> wrote: > >> How about getting the privileged guys to rsync the maven repo so you >> have an internal mirror? Then you'd have the latest maven stuff >> available internally. >> >> See http://maven.apache.org/guides/mini/guide-mirror-settings.html about >> creating your own mirror. >> >> -----Original Message----- >> From: Andreas Guther [mailto:[EMAIL PROTECTED] >> Sent: 23 May 2008 00:26 >> To: Maven Users List >> Subject: RE: Maven Unplugged (no network access) >> >> In your scenario Nexus is not necessary since you are actually not >> proxying anything. If I understand your scenario correctly you need to >> provide a managed and controlled repository. An Apache Server is good >> enough. >> >> I would suggest having the folks with the external access to run the >> builds on their boxes with external access and then after verification >> copy everything from their local repository to the folder from which >> your Apache Maven server serves the artifacts. >> >> Andreas >> >> >> -----Original Message----- >> From: Brian E. Fox [mailto:[EMAIL PROTECTED] >> Sent: Thursday, May 22, 2008 4:03 PM >> To: Maven Users List >> Subject: RE: Maven Unplugged (no network access) >> >> Ouch. Is there any way this "privileged" group can hook up a Nexus to >> the internet, and run through some of your builds? They could then >> analyze and approve the contents which could then be moved to your >> protected instance. Enumerating the full list of things and doing it >> manually is going to be tedious at best. >> >> -----Original Message----- >> From: Seth Geoghegan [mailto:[EMAIL PROTECTED] >> Sent: Thursday, May 22, 2008 11:25 AM >> To: [email protected] >> Subject: Maven Unplugged (no network access) >> >> I am attempting to set up Maven on a corporate network without access >> to >> the web. I've got Maven, a repository (Nexus) and now need to fill my >> repository with all the needed plugins. Unfortunately, I don't have the >> option of letting Maven connect to the web and download its >> plugins/dependencies. Instead, I need to tell a different group >> (non-technical folk) what I need downloaded and they import it onto our >> networks manually. I know it sounds silly, but its the environment I'm >> working in! >> >> Where can I find a list of plugins that Maven needs to support the >> basic >> project lifecycle (compile, test, site, etc)? Any recommendations would >> be >> appreciated. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
