Le mercredi 12 mars 2008, Buck, Robert a écrit : > Hi, > > I probably need my head realigned, but could you help me understand > something? > > I have the settings file below. And what I am doing is the following (or > so I think I am doing this): > > 1. Cache all HTTP downloads into the "download-cache". This is > accomplished by specifying "download-cache" on the "url" based resolver. > When I run the build, I confirm this indeed does work as I anticipated. > Good. > > 2. Define a "Local IVYREP" or sorts in the "ivy/ivyrep" directory. What > I anticipate using this for is for read-only retrievals in case I want > to test an upgrade of some library to a newer version, without impacting > anyone. (Problem, see below) > > 3. Specify to IVY where to put its resolution cache and repository > cache. > > Concerns/Problems: > > 1. The ivy publish commands seem to put the jars from my build in both > the "ivy/cache/repository" directory and the "ivy/ivyrep" directory. > Shuffling around copies of build artifacts is expensive.
If I remember coreectly your cache will be populated as soon as there is a resolve. So the publish will populate your ivy/ivyrep. But on the next resolve that will ask for artifacts in your ivyrep repo, the cache will be populated with them. Nicolas
