无法从中央传输工件 maven-compiler-plugin
我刚刚下载了 Eclipse Indigo 和 m2e 插件,并且此错误显示在我的项目的 pom.xml
中:
ArtifactResolutionException:
Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom:2.3.2
from http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has elapsed or updates are forced.
Original error: Could not transfer artifact org.apache.maven.plugins:
maven-compiler-plugin:pom:2.3.2 from/to central (http://repo1.maven.org/maven2):
null to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom
我发现原始错误消息对于 null
很奇怪>。 我检查了最后一个 url,那里确实有一个 pom
文件。
我尝试在我的 settings.xml
中指定一个镜像,但显然它看起来并不在那里。
另外,当我输入 mvn clean
时,我会收到一条 BUILD SUCCESSFUL
消息。怎么会 ?
谢谢你帮助我。
I have just downloaded Eclipse Indigo and the m2e plugin, and this error shows up in the pom.xml
of my project :
ArtifactResolutionException:
Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom:2.3.2
from http://repo1.maven.org/maven2 was cached in the local repository,
resolution will not be reattempted until the update interval of central has elapsed or updates are forced.
Original error: Could not transfer artifact org.apache.maven.plugins:
maven-compiler-plugin:pom:2.3.2 from/to central (http://repo1.maven.org/maven2):
null to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom
I find the original error message to be weird with the null
.
I checked that last url and there is indeed a pom
file there.
I have tried specifying a mirror in my settings.xml
but it doesn't seem to look there anyway, apparently.
Also, when I type mvn clean
I get a BUILD SUCCESSFUL
message. How come ?
Thank you for helping me out.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
无法获取依赖项的 POM 不被视为错误。这只是一个警告。这解释了为什么
mvn clean
会成功。至于不咨询您的设置,您是否确保已将 M2E 配置为使用您的设置文件?Failure to get the POM for a dependency is not considered an error. It is just a warning. This explains why
mvn clean
is successful. As far as your settings not being consulted have you ensured that you have configured M2E to use your settings file?