You asked...

I agree that the Nexus pull only when needed is nice. But there are other
concerns too. The real question is there a strong reason for not using rsync
other than use Nexus.


Yes.

   1. I use nexus so that I limit the bandwidth I share with YOU (from
   hosted repositories). No one likes a 'road hog' :)
   2. Nexus will allow you to proxy/mirror a lot more than one repository,
   it will also allow you to place rules on repositories and additional
   configuration.
   3. Nexus will be useful as it provides you with your own maven
   repository to deploy/release your own artifacts/projects too.
   4. Nexus can aggregate a bunch of repositories into "one" virtual
   repository, this will make life easier for your developers as they only
   ever need 1 repository.
   5. Nexus can provide you with a place to "upload"/"deploy" artifacts
   that are not in a public repository so that they can be shared with your
   team members.
   6. Because its "the standard", if you want to re-invent the wheel that's
   cool, it'll do very much the same job. Alternatively there is a bunch of
   documentation out there about nexus and its application, setup, usage,
   settings.xml e.t.c.... Just in case you get hit by a bus or win the lottery
   next week you'll be a lot less vulnerable.


Hope that helps :)



On Mon, Apr 23, 2012 at 1:26 AM, Jason Pyeron <jpye...@pdinc.us> wrote:

> > -----Original Message-----
> > From: Brian Topping
> > Sent: Sunday, April 22, 2012 11:32
> >
> > On Apr 22, 2012, at 10:26 AM, Jason Pyeron wrote:
> >
> > > 1. Is mirrors.ibiblio.org a good source for mirroring
> > repo1.maven.apache.org?
> > > 2. is there a strong reason not use rsync?
> >
> > Mirroring a repository like that is considered very bad form
> > and will probably get your servers blacklisted.
>
> This caught me off guard. Is that not the point of ibiblio.org supporting
> rsync?
> We have a daily rsync set up with them for other projects.
>
> >
> > I don't have the benefit of other posts you may have made on
> > this subject,
>
> No other posts on this topic.
>
> > but unless you are hosting half the known world
> > of developers, why wouldn't you just use a repository?
>
> The mirror team has bandwith management infrastructure inplace. They did
> not
> want to modify their system to support Nexus for Nexus sake. We have a
> nexus
> server on our dev lan already. Our dev lan does not have direct access to
> the
> internet.
>
> > It
> > makes things so much simpler with your builds since real
> > world projects generally do not pull from just central.
>
> It was listed on the bandwidth report.
>
> > Having a half-dozen repositories in your build is a great way
> > to have it constantly slow (and even slower at times when any
> > one of those repositories is offline).  Caching those
> > repositories through Nexus insulates you from their downtime,
> > without having to soak their bandwidth for files you will never use.
>
> I agree that the Nexus pull only when needed is nice. But there are other
> concerns too. The real question is there a strong reason for not using
> rsync
> other than use Nexus.
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> -                                                               -
> - Jason Pyeron                      PD Inc. http://www.pdinc.us -
> - Principal Consultant              10 West 24th Street #100    -
> - +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
> -                                                               -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to