Hi David. I am too busy to try, but here is a quick idea: You could use Maven Dependency Plugin, e.g. mvn dependency:tree. That should resolve your dependencies. If you want to be 100% sure to resolve all dependencies, also plugin-related ones, you could use dependency:go-offline.
Alexander Kriegisch https://scrum-master.de David Karr schrieb am 01.06.2023 um 23:05: > We have a situation in our build environment where Maven concludes it can't > get certain artifacts, resulting in a build failure message like this: > > [ERROR] Failed to execute goal on project ..: Could not resolve > dependencies for project ...:jar:1.1.0-SNAPSHOT: The following > artifacts could not be resolved: ...: Could not find artifact ... -> > [Help 1] > > > The problem happens to be a corruption of the artifact on the local maven > repo on the build node (the jar file fails to download for some reason). > > We are working on a robust solution to prevent these, but right now each > one of these incidents is resolved by purging that particular artifact on > the particular build node and letting the build rerun. > > The problem is (among others) is that when this happens, it almost always > happens with more than one artifact. As a result, when I run the build > after the offending artifact is purged, it only shows me the next artifact > it fails on. This goes on for several iterations before it finally works > again. > > What I want to know is whether there is any way to tell "mvn" to give me > ALL of these errors at once, instead of stopping the build at the first one. > > Is this what "--fail-at-end" would do for me, or would that have other > unintended consequences? > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
