How to force maven update?

Question

I imported my already working project on another computer and it started to download dependencies.

Apparently my internet connection crashed and now I get the following:

    >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

How do I force maven to update?

Side note: I had this issue with Atlassian Maven (from plugin SDK) and upgrading to newer version solved the problem. — Wirone, Oct 08 '15 at 05:04

score 1894 · Accepted Answer · edited Apr 21 '21 at 17:14

1894

mvn clean install -U

-U means force update of snapshot dependencies.

Release dependencies will be updated this way if they have never been previously successfully downloaded. ref: https://stackoverflow.com/a/29020990/32453

edited Apr 21 '21 at 17:14

rogerdpack

62,887
36
269
388

answered Mar 14 '12 at 08:06

Jackie

25,199
6
33
24

38

I agree with lwpro2, this solved my problem as well. Just doing mvn clean isn't enough. The answer of Navi is not enough to solve the problem. – R. van Twisk Jul 19 '12 at 22:15
1

I believe this is more complicated if you were using artifactory and used the repository id "central", because the metadata doesn't apparently get cleaned out. – ggb667 May 12 '14 at 20:45
3

This doesn't seem to actually update the snapshot dependency jars, just the metadata. – Roddy of the Frozen Peas Nov 05 '15 at 21:33
1

if it's caused by the .lastupdated file, generated from the last unsuccessful dependency downloading, this method will not work, we need something like Rober Reiz's answer – Junchen Liu May 04 '16 at 10:44
1

I'm looking at the help for previous versions and up to maven 2.0.4, the description for the -U flag was: "-U,--update-snapshots Update all snapshots regardless of repository policies" starting with 2.0.5, it became: " -U,--update-snapshots Forces a check for updated releases and snapshots on remote repositories" And it's been like that since then. Both versions were released in 2007. I wonder if the answer must be edited to account for the releases, too? – cleberz Nov 03 '17 at 20:15
How does one do this in an IDE such as IntelliJ 2018? – Basil Bourque Oct 01 '18 at 03:16
actually, `mvn compile -U` should suffice in many cases, right? – Qw3ry Apr 08 '20 at 06:58

score 147 · Answer 2 · edited May 17 '17 at 01:40

147

If your local repository is somehow mucked up for release jars as opposed to snapshots (-U and --update-snapshots only update snapshots), you can purge the local repo using the following:

 mvn dependency:purge-local-repository

You probably then want to clean and install again:

 mvn dependency:purge-local-repository clean install

Lots more info available at https://maven.apache.org/plugins/maven-dependency-plugin/examples/purging-local-repository.html

edited May 17 '17 at 01:40

Nathan

8,093
8
50
76

answered Nov 26 '15 at 02:46

FuzzyJulz

2,714
1
16
18

19

As soon as I did `mvn dependency:purge-local-repository`, it simply re-downloaded all the dependencies again, which is exactly what I wanted – smac89 Apr 05 '18 at 15:48
https://stackoverflow.com/questions/71176805/in-xhtml-page-jsf-attribute-are-not-rendering @FuzzyJulz – ritu mansata Feb 19 '22 at 12:44

score 113 · Answer 3 · edited Apr 21 '21 at 17:09

113

-U seems to force update of all SNAPSHOT dependencies.

If you want to update a single dependency without clean or -U you could just remove it from your local repo and then build.

The example below if for updating slf4j-api 1.7.1-SNAPSHOT:

rm -rf ~/.m2/repository/org/slf4j/slf4j-api/1.7.1-SNAPSHOT
mvn compile

edited Apr 21 '21 at 17:09

rogerdpack

62,887
36
269
388

answered Mar 11 '13 at 10:31

Ayush Gupta

5,568
2
21
17

This works nicely if you're using another tool other than maven that references your local maven repository. – Mansoor Siddiqui Oct 16 '15 at 21:31
https://stackoverflow.com/questions/71176805/in-xhtml-page-jsf-attribute-are-not-rendering @Ayush Gupta – ritu mansata Feb 19 '22 at 12:44
I used this to update a single snapshot version of a library which was cached locally, but had changed remotely. This is faster than `mvn clean ...` when you have many dependencies. – Lucio Paiva May 10 '22 at 11:21

score 66 · Answer 4 · edited Jan 25 '16 at 10:15

66

All the answers here didn't work for me. I used the hammer method:

find ~/.m2/ -name "*.lastUpdated" | xargs rm

That fixed the problem :-)

edited Jan 25 '16 at 10:15

Jens

67,715
15
98
113

answered Nov 17 '14 at 14:17

Robert Reiz

4,243
2
30
43

1

@DJ2 This deletes all files in the `.m2`-directory named `*.lastUpdated` – sjngm Dec 17 '18 at 07:51
1

`find ~/.m2/ -name "*.lastUpdated" -delete` would do without the danger of `xargs` or `rm` exceeding some limits (if many files are found). – A Sz Feb 03 '20 at 14:34
1

@ASz `xargs` reads the arguments from stdin, which shouldn't have any limits. It then splits the arguments into multiple `rm` calls if the number of arguments exceeds the system-defined limit. The `xargs rm` version shouldn't fail on limits, but doing it in one `find` call is of course still nicer (and shouldn't fail if a file name contains a newline). – jazzpi Dec 15 '20 at 08:27

score 46 · Answer 5 · answered Feb 06 '14 at 09:28

46

You can do effectively from Eclipse IDE. Of course if you are using it.

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

answered Feb 06 '14 at 09:28

Amit Shakya

1,396
12
27

1

I did the command line version in the answer by @lwpro2, which let me build *on the command line*, but then I still could not build within Eclipse. Doing this got it to build through Eclipse. – Brick Jul 15 '16 at 02:31
Works for me only if I close and reopen Eclipse after executing the update. – ceklock Jan 02 '17 at 16:58
https://stackoverflow.com/questions/71176805/in-xhtml-page-jsf-attribute-are-not-rendering @Amit Shakya – ritu mansata Feb 19 '22 at 12:45

score 46 · Answer 6 · answered Jul 05 '17 at 09:01

Just in case someone wants only update project's snapshot dependencies and doesn't want to install artifact:

mvn dependency:resolve -U

Don't forget to reimport dependencies in your IDE. In IDEA you need to right click on pom file and choose Maven -> Reimport

score 14 · Answer 7 · answered May 24 '13 at 15:42

14

If you're unsure what is inside your local repository, I recommend to fire a build with the option:

-Dmaven.repo.local=localrepo

That way you'll ensure to build in a cleanroom environment.

answered May 24 '13 at 15:42

merejy

414
4
17

5

this command means use folder localrepo to be the local repository. that is fine for a single project workspace but bad if you have more than one project, and few depend on the other. then your better of giving a full path like -Dmaven.repo.local=/data/my/localrepoDir – tgkprog Aug 25 '13 at 10:45

score 12 · Answer 8 · edited Aug 15 '19 at 14:06

12

In my case first I did was:

mvn clean install -U

Still it was showing same error then I closed project and again reopened it. Finally worked.

edited Aug 15 '19 at 14:06

Ihor Patsian

1,288
2
15
25

answered Jul 22 '14 at 03:56

rajeev

499
1
8
17

1

I think you could just do reimport dependencies to avoid reopening the project – GlaIZier Jul 05 '17 at 09:03

score 7 · Answer 9 · edited Aug 28 '19 at 13:17

7

If you are using eclipse IDE then :

Select Project.
Press alt+F5, window for Update Maven Project will pop up.
Check - Force Update of Snapshots/releases and click OK.

If Using Intellij IDE

go to settings/Maven
check Always update snapshots

edited Aug 28 '19 at 13:17

Davis Broda

4,102
5
23
37

answered Sep 19 '18 at 05:20

patidarsnju

439
5
10

score 6 · Answer 10 · answered Nov 18 '19 at 14:48

6

I used the IntelliJ IDE and I had a similar problem and to solve I clicked in "Generate Sources and Update Folders for All Projects" in Maven tab.

answered Nov 18 '19 at 14:48

Willyan

123
2
7

score 6 · Answer 11 · answered Nov 28 '19 at 11:00

Previous versions of maven did not force the check for missing releases when used -U with mvn clean install, only the snapshots, though newer version supports this.

For someone still struggling with previous version, following can be helpful-

On Windows:

cd %userprofile%\.m2\repository
for /r %i in (*.lastUpdated) do del %i

On Linux:

find ~/.m2  -name "*.lastUpdated" -exec grep -q "Could not transfer" {} \; -print -exec rm {} \;

Whenever maven can't download dependencies for any reason (connectivity/not exists etc), it will add the ".error=Could not transfer artifact" in dependency-name.lastUpdate file in respective folder under $home/.m2 directory. Removing these files will force maven to try fetching the dependencies again.

Can you name, which "previous" and "newer" versions you are talking about and where you found the information, that "newer" versions support this? — Tobias Liefke, May 18 '22 at 07:59

score 4 · Answer 12 · answered Sep 29 '22 at 10:55

mvn clean install -e -U -Dmaven.test.skip=true

-e Detailed exception
-U forced update
-DskipTests does not execute test cases, but compiles test case classes to generate corresponding class files under target/test classes.
-Dmaven.test.skip=true, do not execute test cases or compile test case classes.Using maven. test. skip not only skips running unit tests, but also skips compiling test code.

A small suggestion. If you use the IntelliJ Idea compiler, it is recommended to clean the cache

score 2 · Answer 13 · answered Nov 19 '13 at 22:53

I've got the error in an other context. So my solution might be useful to others who stumple upon the question:

The problem: I've copied the local repository to another computer, which has no connection to a special repository. So maven tried to check the artifacts against the invalid repository.

My solution: Remove the _maven.repositories files.

score 2 · Answer 14 · edited Aug 18 '18 at 02:04

2

You need to check your settings.xml file under <maven_home>/conf directory.

edited Aug 18 '18 at 02:04

Bhargav Rao

50,140
28
121
140

answered Jul 25 '17 at 08:08

Ashish Nariyal

21
1

score 1 · Answer 15 · answered Apr 20 '15 at 06:13

1

This is one of the most annoying things about Maven. For me the following happens: If I add a dependency requesting more dependencies and more and more but have a slow connection, it seams to stop while downloading and timing out. While timing out all dependencies not yet fetched are marked with place holders in the .m2 cache and Maven will not (never) pick it up unless I remove the place holder entry from the cache (as other stated) by removing it.

So as far as I see it, Maven or more precise the Eclipse Maven plugin has a bug regarding this. Someone should report this.

answered Apr 20 '15 at 06:13

Martin Kersten

5,127
8
46
77

"Someone should report this." - and that someone should be you :) – Line Oct 21 '20 at 08:04
I do not felt entitled to do so... . People with way better understanding of the matter must step up... . – Martin Kersten Oct 21 '20 at 11:46
they didn't for 5 years (or we don't know about it), so the only hope is in you ;) – Line Oct 22 '20 at 09:17

score 1 · Answer 16 · answered Mar 12 '17 at 09:30

It's important to add that the main difference of running mvn with -U and without -U is that -U will override your local SNAPSHOT jars with remote SNAPSHOT jars.

Local SNAPSHOT jars created from local mvn install in cases where you have other modules of your proj that generate jars.

score 1 · Answer 17 · edited Mar 19 '17 at 09:50

For fixing this issue from Eclipse:

1) Add below dependency in Maven pom.xml and save the pom.xml file.

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

2) Go to project >> Maven >> Update Project

select the project and click OK.

3) Optional step, if it's not resolved till step 2 then do below step after doing step-1

Go to project >> Maven >> Update Project >> check in the checkbox 'Force Update of Snapshots/Releases'

select the project and click OK.

score 1 · Answer 18 · answered May 01 '18 at 17:08

1

-U is used to force update maven Repo. Use

mvn -U clean install

answered May 01 '18 at 17:08

Sanjeev Guglani

2,114
1
7
13

@KerwinSneijders I had added answer 2years ago at that time , accepted answer did not provide information about what -U does here – Sanjeev Guglani Apr 23 '20 at 16:02

score 0 · Answer 19 · answered May 23 '16 at 14:35

0

I've got the same error with android-maps-utils dependency. Using aar type package in dependency section solve my problem. By default type is jar so It might be checked what type of dependency in repository is downloaded.

answered May 23 '16 at 14:35

zhen_khokh

69
1
8

score 0 · Answer 20 · answered Feb 25 '19 at 09:29

0

I tried all the answers here but nothing seemed to work. Restarted my computer first then ran mvn clean install -U. That solved my problem.

answered Feb 25 '19 at 09:29

Gelo

105
10

score 0 · Answer 21 · answered Apr 17 '19 at 17:12

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

score 0 · Answer 22 · answered Jan 21 '22 at 07:14

0

after using mvn clean install -U run as maven test also and after that update your project using maven-update project this works in my case

answered Jan 21 '22 at 07:14

ritu mansata

77
2
13

1

There is no `maven-update` command. Please review your answer. – Rade_303 Jan 21 '22 at 16:53
i am not talking about maven-update command,just right click on project ,select maven then select update project option @Rade_303 – ritu mansata Jan 21 '22 at 17:06
Which IDE are you talking about? Regardless, the answer should be about maven as a command line tool, not about maven integration in some IDE. – Rade_303 Feb 15 '22 at 00:08
i am talking about eclipse IDE@Rade_303 – ritu mansata Feb 16 '22 at 03:13
the user is probably not using Eclipse – Rade_303 Nov 25 '22 at 13:14

score -2 · Answer 23 · answered Nov 21 '16 at 18:01

I had this problem for a different reason. I went to the maven repository https://mvnrepository.com looking for the latest version of spring core, which at the time was 5.0.0.M3/ The repository showed me this entry for my pom.xml:

<!-- https://mvnrepository.com/artifact/org.springframework/spring-core -->
<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-core</artifactId>
    <version>5.0.0.M3</version>
</dependency>

Naive fool that I am, I assumed that the comment was telling me that the jar is located in the default repository.

However, after a lot of head-banging, I saw a note just below the xml saying "Note: this artifact it located at Alfresco Public repository (https://artifacts.alfresco.com/nexus/content/repositories/public/)"

So the comment in the XML is completely misleading. The jar is located in another archive, which was why Maven couldn't find it!

score -3 · Answer 24 · edited Jun 15 '15 at 09:51

-3

We can force to get latest update of release and snapshot repository with below command :

mvn --update-snapshots clean install

edited Jun 15 '15 at 09:51

josliber

43,891
12
98
133

answered Jun 15 '15 at 09:49

sopheak Seng

17
3

15

This is the exact same answer as the accepted answer. -U is the short form of --update-snapshots. – Roddy of the Frozen Peas Nov 05 '15 at 21:28

score -4 · Answer 25 · edited Mar 10 '16 at 19:27

-4

I had the same error and running mvn install -U and then running mvn install worked for me.

edited Mar 10 '16 at 19:27

Martin Tournoij

26,737
24
105
146

answered Mar 10 '16 at 19:10

rich_markle

13
6

11

Please don't post *"the thing mentioned in all the other answers worked for me too"* answers. – kryger Oct 17 '16 at 14:00

score -6 · Answer 26 · answered Aug 22 '14 at 12:33

-6

mvn clean install -U doesn't work. However mvn -U clean followed by mvn clean install does.

answered Aug 22 '14 at 12:33

mroman

1,354
9
14

How to force maven update?

26 Answers26

Linked

Related