Maven依赖中类似was cached in the local repository样的错误
浏览数：28 /
时间：2015年06月20日
我们在使用maven编译一个项目时经常会遇到诸如此类的问题。
Could not get the value for parameter encoding for plugin execution default-resourcesPlugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failure to find org.codehaus.plexus:plexus-utils:jar:1.1 in http://nexusserver:8081/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of mirr...
was cached in the local repository, resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced ->
大体意思是jar包没有下载完整，不过也要分两种情况。
一种可能就是本地没有下载完整，这里的原因可能第一次下载由于网络原因不成功，之后maven也没在尝试。
引用
This is often a false positive. Imagine you have a connection issue lasting only 5 seconds when Maven 3 tries to download a dependency, it will mark this dependency as unavailable for a delay. And thus will prevent you from replaying the build command even if the network issue is fixed.
Just run the command with the -U option. Even if its description applies to snapshots, it seems to also fix the error if it occurred on a release.
Example: mvn -U clean package
This is often a false positive. Imagine you have a connection issue lasting only 5 seconds when Maven 3 tries to download a dependency, it will mark this dependency as unavailable for a delay. And thus will prevent you from replaying the build command even if the network issue is fixed.
Just run the command with the -U option. Even if its description applies to snapshots, it seems to also fix the error if it occurred on a release.
Example: mvn -U clean package
此外，我们可以在setting.xml中增加updatePolicy策略
setting.xml指导
在setting.xml的schema中有这样一个描述
schema
另一种情况就是我们依赖的nexus也没有下载完整，这时候可能是配置的中央仓库代理仓库根本就不存在此jar，或者需要在第三方仓库中才能找到，此时我们应该尝试检查和配置代理仓库。
郑重声明：本站内容如果来自互联网及其他传播媒体，其版权均属原媒体及文章作者所有。转载目的在于传递更多信息及用于网络分享，并不代表本站赞同其观点和对其真实性负责，也不构成任何其他建议。
