I believe this is due to the id of the repo used changes. Maven 3 keeps track of which repo it used to download an artifact (which Maven 2 didn't). So if it changes it re-downloads to prevent issues due to artifact being different (which shouldn't be the case in a perfect world, but still happens).
/Anders On Fri, Nov 27, 2015 at 11:19 AM, Thomas Meyer <tho...@m3y3r.de> wrote: > Hi, > > I have the impression that changing the maven central mirror in the > settings.xml does result in redownloading of all dependencies?! > Why is that the case? > Can I supress this? I.e. the artifacts are actually the same! > > With kind regards > Thomas >
