mvn-sync: Build after redeploying a fixed version of a previously broken artifact fails due to maven caching

[Aklakan]

Running mvn deploy to upload an artifact e.g. with an incorrect pom* causes the server-side mvn-sync build process to fail with the message that the pom could not be resolved.
After deploying an artifact with a correct pom later still causes the server-side build to fail because the error has been cached in its maven repository.
Running maven mvn -U deploy on the server for the conflicting artifact fixes the problem, but as this downloads all snapshot dependencies, it is thus is far from ideal to run -U on every dataset upload.

Maybe mvn dependency:purge-local-repository or similar can be used to clear a broken dataset artifact.

*Using the Archiva "Upload Artifact" form even allows uploading artifacts without a pom.xml.