我将我已经工作的项目导入到另一台计算机上,它开始下载依赖项。

显然我的网络连接崩溃了,现在我得到了以下信息:

    >Build errors for comics; org.apache.maven.lifecycle.LifecycleExecutionException:
    Failed to execute goal on project comicsTest: Could not resolve dependencies for project comicsTest:comicsTest:war:0.0.1-SNAPSHOT:
    The following artifacts could not be resolved:
    org.springframework:spring-context:jar:3.0.5.RELEASE,
    org.hibernate:hibernate-entitymanager:jar:3.6.0.Final,
    org.hibernate:hibernate-core:jar:3.6.0.Final,
    org.hibernate:hibernate-commons-annotations:jar:3.2.0.Final,
    org.aspectj:aspectjweaver:jar:1.6.8,
    commons-lang:commons-lang:jar:2.5,

    >mysql:mysql-connector-java:jar:5.1.13: Failure to transfer org.springframework:spring-context:jar:3.0.5.RELEASE 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.springframework:spring-context:jar:3.0.5.RELEASE from central (http://repo1.maven.org/maven2): No response received after 60000

如何强制maven更新?


当前回答

-U用于强制更新maven Repo。 使用

mvn -U clean install

其他回答

mvn clean install -U不工作。但是mvn -U clean后面跟着mvn clean install。

您可以从Eclipse IDE中有效地完成这些工作。当然,如果你在用的话。

Project_Name->Maven->Update Project Configuration->Force Update of Snapshots/Releases

这是Maven最烦人的事情之一。对我来说,会发生以下情况:如果我添加了一个依赖项,请求更多的依赖项,但是连接很慢,它会在下载和超时时停止。在计时时,所有尚未获取的依赖项都在.m2缓存中用占位符标记,Maven不会(永远不会)拾取它,除非我通过删除它从缓存中删除占位符条目(如前所述)。

所以就我所知,Maven或者更准确的说是Eclipse Maven插件在这方面有一个bug。应该有人报告此事。

要从Eclipse中修复此问题:

1)在Maven pom.xml中添加以下依赖项,并保存pom.xml文件。

<!-- https://mvnrepository.com/artifact/com.thoughtworks.xstream/xstream -->
<dependency>
    <groupId>com.thoughtworks.xstream</groupId>
    <artifactId>xstream</artifactId>
    <version>1.3.1</version>
</dependency>

2)进入项目>> Maven >>更新项目

选择项目并单击OK。

3)可选步骤,如果到第2步还没有解决,在第1步之后再执行下一步骤

转到项目>> Maven >>更新项目>>检查复选框中的“强制更新快照/发布”

选择项目并单击OK。

What maven does is, it downloads all your project's dependencies into your local repo (.m2 folder). Because of the internet causing issues with your local repo, you project is facing problems. I am not sure if this will surely help you or not but you can try deleting all the files within the repository folder inside the .m2 folder. Since there would be nothing in the local repo, maven would be forced to download the dependencies again, thus forcing an update. Generally, the .m2 folder is located at c:users:[username]:.m2