Maven will cache artifacts locally and if you have a dependency on a non-snapshot version of the artifact, it only ever gets downloaded once. From then on, it assumes that the version in your local repository is current. Right?
If you have a dependency on a snapshot version it will attempt to download it from a remote repository, which you can define to be e.g. ibiblio to completely bypass any use of apache resources. (Of course, this means that it increases the load on ibiblio but they've signed up to be an apache mirror so they presumably know the drill).
The way we use maven is that the snapshot version dependencies are on artifacts that can be built locally; that is, they just don't exist on the remote repository, so maven can't find them remotely. This can't be much of a load. Returning a 440 reply to a maven request isn't expensive... Right?
I'm sure I'm missing something obvious, and I would like to know where I've gone off the rails...
Thanks, Craig On Jun 7, 2006, at 12:57 PM, Henri Yandell wrote:
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote: > > > And in any case, I believe that much of the problem > > is not with maven per se, but with how it is being used. > > How exactly? >> Cocoon/Geronimo have both hit the same problem. The factor would seem > to be having a lot of components in your build - which I can't see as> being a mis-use. The part about pointing to people.apache.org as a maven repository isnot a design flaw in maven. The part about maven gobbling up way moreresources than necessary probably is.Geronimo/Cocoon and other projects did not set up the maven snapshot repository at the ASF, they're using what has been in place for a long time. Hen
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
