Well I haven't actually done it but I think you can use Ivy in an 'offline' mode by slightly tweakng your cache settings to not check the source repo for update. There is some description in a bug report (!) here:
https://issues.apache.org/jira/browse/IVY-879 I don't know if this is an option for you but we've just started using Archiva as a maven proxy. You can proxy all your repos together into a single source very easily. I'm tempted to run it on my laptop to save bandwidth. http://archiva.apache.org/ Cheers, Geoff On Thu, May 13, 2010 at 7:10 AM, Valerie Wagner <[email protected]>wrote: > Thanks Mitch & Geoff. I actually went with something similar to Geoff's > solution. Now I have a new problem. > > We host our third-party libraries on "our-ivy-server". When I build the > system, they are downloaded and cached. When I switch to the "local" > settings, the Ivy resolve fails to find the third-party libraries because > "our-ivy-server" is not part of the local settings. Or perhaps Ivy does find > them in the cache, but it puts out the message "unknown resolver > our-ivy-server" a few times during the resolve process. > > The only thing I have thought of so far is to make the local settings have > another filesystem resolve in it, called "our-ivy-server" but have it point > at the cache directory. That seems ugly as well. Anyone have another idea? > > thanks much for the help! > > Valerie >
