That was great advice, Bernd. I never was aware of that goal before,
mostly using the 'analzye' and 'tree' goals. I also see that it is
possible not use includes and excludes, i.e. to just purge what annoys
you and not a whole 60 GB or so local repo. For reference:
-U works on release artifacts as well. Alternatively you can delete the version
(either manually in the filesystem or with a maven
dependency:purge-local-repository).
I think the Never-policy was not meant to deal with errors, it is more about
immutability of the actual releases.
Gruss
Bernd
Hi fellow Maven users,
I have used Maven for 10 years or more and I’m writing with a first. I have a
project which was set up in Jenkins with a settings.xml that has updatePolicy
set to “never” for a certain repository.
I have experienced that when Maven 3.3.9 fails to resolve an artifact for
