ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <ste...@apache.org>
Subject making an SCM managed copy of your external artifacts
Date Mon, 09 Aug 2010 11:24:35 GMT

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?

Mime
View raw message