ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: CVS Resolver
Date Wed, 28 Apr 2010 12:39:57 GMT
That is a good point on the size. They will not reach no more than 500MB across their projects
initially; however, that could grow quite a bit. 
There are several reasons. The CVS server is existing, has all the user accounts setup, provides
security/control over who can add to the repository and is being backed up nightly. Again,
if I had my way, I would use Archiva or Artifactory, but I am concerned with pitching a process
change that introduces another product with maintenance and support required. 


From: Tim Brown []
Sent: Tue 4/27/2010 6:13 PM
Subject: Re: CVS Resolver

Haven't seen this before -- and I'd be wary of putting an Ivy repository
into CVS.

I can't speak for others, but we're generating a good 100GB of binaries with
each release (yes, we're a really big stack).  CVS' handling of binary files
isn't great, and you're going to create a really large CVS repository

Why do you want to put binaries into CVS?

On Tue, Apr 27, 2010 at 3:29 PM, <> wrote:

> I am looking to pitch Ivy for DM on a project; however, one of the
> obstacles I came across was getting an interface to install to and resolve
> from a CVS-based repository. Has anyone tried this before? I am looking for
> some direction and could not find much on the web.
> We have looked at archiva and artifactory as a replacement option for a cvs
> repo, but we fear that it will hurt our position, where using the existing
> cvs setup would strengthen it.
> We are using extssh for our connection to cvs and thought of potentially
> extending the ssh resolver for this purpose.
> Sincerely,
> Michael

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message