Ruchith Fernando wrote:
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.
IMHO this problem will only occur IFF we have SNAPSHOT dependencies,
since a jar of a released version cannot change. We are trying stick
to a released version of all the projects that axis2 is dependant on
before a particular release ... then this problem will not be there.
This still appears to be a maven bug, if there's no way of turning off
the repeated checks. If you *are* using SNAPSHOT dependencies it creates
the opportunity for an apparently successful built that results in a
broken distribution (because a SNAPSHOT changed in the middle of your
build). If you're not using SNAPSHOT dependencies it means that maven is
checking the same file repeatedly, which is a waste of time - in fact,
why should it check at all in this case, since the file will always be
the same.
- Dennis
