Hi, I'm new to maven, and I'm a bit reserved to trusting a few centralized servers for something that's critical to a project.

Since any host that downloads a project (say, from SVN) and wants to build it, needs to download a number of Maven packages, obviously there's a heavy dependency on the central maven server.

Yesterday when I started trying out Maven, I spent maybe 20 minutes waiting for the initial dependencies to be loaded from repo.maven.org (at speeds of a few to a few thousand bytes/second), until I found out how to use a mirror site. The problem: there are only a handful of mirror sites, and should they disappear (for any reason, maybe the company/organisation losing interest / moving to another build system) or be as overloaded/slow as the central server, it'd be impossible to setup a new host and work on the project.

I've read through the docs a bit and found out that you can set up your own servers, but my question: is there a list of what packages/ dependencies the maven core uses, so that anybody who wants a 100% reliable server can download anything that maven could ever need (only the builtin modules, obviously; for everything else you manage your own dependencies).

Is it a viable option to simply tar up the .m2 directory after a few full project builds (so that hopefully all dependencies will have been loaded).

This isn't a troll, I'm only genuinely afraid of trusting a few centralized servers for a task that's needed for any new machine to setup their system (especially after noticing last night, how slow a server can be and what that means for getting to work). A big tarball/package would certainly be easier to deploy for an organisation.

Best regards,
  Ulrich

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to