Bill Nagy wrote:
In my experience (and maybe others have different problems) the longest
delays are caused by the repositories not responding/timing out. The -o
option is the only way to get around this, as otherwise even the hash
comparison will cause the timeouts. Unfortunately if you have an out-
of-date dependency, as often happens, you're out of luck. You can use a
caching proxy to help out, but you still have to worry about keeping the
cache current.
Timeouts are a serious problem, but I find maven annoying even when the
repositories respond - there's a noticeable delay for each check, and
the same exact jars are repeatedly checked (and often repeatedly
downloaded, it seems, though I don't know why). Isn't there a way to
tell maven it should only try updating each particular jar once within a
build?
The fact that it checks repeatedly smells like a bug to me. Consider
what happens if the jar changes in the middle of your build - you have
some code built using the old version of the jar, and some with the new.
That's dangerous at best, since it means you could end up shipping a
broken distribution.
Hopefully someone with a better knowledge of maven can comment on these
issues.
- Dennis
