On Jul 28, 2006, at 1:28 PM, Graham Leggett wrote:
On Fri, July 28, 2006 1:06 pm, Ulrich Hobelmann wrote:
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.
This is only a once off problem - now that you've gone through the
doanloading pain, there is no need to do it again, unless you
decide to
add or change versions of dependancies.
Ok, that sounds reasonable.
Could I simply tar up the .m2 directory, or is there anything in it
that's host-specific? (so a new machine could simply copy the .m2
and start building; especially for a portable machine I'd hate to be
missing a dependency...).
The full repository is quite a number of GB in size, making a tarball
available of it is unlikely to be efficient when you could simply
mirror
the repository yourself from time to time, removing the risk of the
repo
"going away".
If the central repos go down, you lose the auto-download
capability, but
there is nothing stopping you from resolving the dependencies manually
(apart from the annoyance of having to do so).
Ok, thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
