Hi, I've used 'both approaches'
1. Use Ivy to build and maintain the repo - I use a master Ivy file with all the deps we use specified and then a resolve and rsync to the enterprise repo (which is Apache httpd). This also holds our shared ivy settings. This way I have more control over what goes into the enterprise repo. 2. We recently used Archiva on a different repo. It was in many ways harder to get running (how we wanted) but does have the advantage of acting more like a persistent proxy for central etc. This also means developers are in control of what gets into this enterprise repo. Either way work fine I think the only real difference for us is who controls what gets into the repo. If you're pushing a lot of jars then the search features of some of the archive managers may be nice. Cheers, Geoff On Mon, Aug 9, 2010 at 11:24 PM, Steve Loughran <[email protected]> wrote: > > I want to set up a project which has all the things we depend on in SCM, > plan is to have two repositories > > repo/internal - in house built artifacts, SCM managed release propagation, > etc. > > repo/external - everything that normally comes out of ibiblio, jboss, > reslet m2 repositories, which ivy pulls down, and the odd Sun JAR that isn't > normally online > > Question is, how best to build that external repository, especially, how > best to automate building that repository. > > > 1. Manual M2 layout. From the dependency data, grab the JARs and POM files, > lay them out maven style. > > 2. Copy ivy cache. clean your local cache, do a release, copy ~/.ivy/cache > to repo/external, delete things you don't want there and check in the rest. > > Has anyone else done this? What was their tactic? >
