I totally agree. Apart from saving you lots of bandwidth a repository manager
will also allow you to host artifacts that can not live on repo1 like
proprietary jdbc drivers and so on. You will also be able to release your
internal libraries to it and therefore share them better amongst your team an
Far better is just to run a maven repository manager at your site.
e.g. nexus, artifactory, etc
They are easy to set up (at least I find nexus trivial)
They will permanently cache all the artifacts that you use, which should
meet your requirements and save you from chasing the 70GB+ of rsync
-S
To whom it may concern,
I am currently working at National Cancer Institute. They have a policy
related to build processes that all resources used to build code at NCI need
to be hosted locally. Several months ago we started rsyncing the ibiblio
mirror site locally (rsync -v -t -l -r --exclu
