Workaround for maven dependent jar download failure

There is a situation in the MAVEN project where the specified dependent jar packages are not shown in the project, but the build period specifies the third-party plug-ins that rely on many other jar packages that are also required to be downloaded to the local repository, otherwise they will be error-free, for example:

Failure to find org.codehaus.plexus:plexus-io:jar:2.0.5 in Http://xxx.xxx.xxx:8089/nexus/content/groups/cninfo_ Group is cached in the local repository, resolution is not being reattempted until the update interval of central have El apsed or updates is force.

The solution at this time is:

1) If the network is not good enough to download the jar package from the central repository via Nexus, remove the third-party plugin

2) If the network is good, go to the local repository directory, delete the directory that cannot download the jar package, such as the org/codehaus/plexus/plexus-io/2.0.5 directory, and then modify the Pom.xml file to download the jar package from the central repository from the new

This article from "Small Fish Blog" blog, declined reprint!

Workaround for maven dependent jar download failure