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?
