Maven fails to find local artifact

Question

Occasionally maven complains that a particular dependency  which is built and packaged locally  cannot be found in the local repository while building another project that has it as a dependency   We get an error like      Failed to execute goal on project X  Could not resolve dependencies for project X  Failure to find Y in  archiva repository  was cached in the local repository  resolution will not be reattempted until the update interval of internal has elapsed or updates are forced -    Where X is the project being built  and Y is the supposedly missing artifact   If you look in the local repository  the artifact is there   This artifact is never installed in our archiva repository  so the problem is purely based in the local repository   We have tried various profiles in settings xml  and of course  mvn -U    Neither do any good  nor should they because this artifact never goes any further than the local repository   The only two things that seem to work are to wait a very long time until maven smartens up  or to completely delete the local repository   Presumably the waiting option is related to the aforementioned update interval   We have experienced this problem with maven 3 0 2 and 3 0 3   We are using Archiva 1 0 3  but again this shouldn t be a factor    Any help would be greatly appreciated

User · Answer

I had DependencyResolutionException in Ubuntu Linux when I ve installed local artifacts via a shell script  The solution was to delete the local artifacts and install them again  manually  - calling mvn install install-file via terminal

User · Answer

When this happened to me  it was because I d blindly copied my settings xml from a template and it still had the blank  lt localRepository  gt  element   This means that there s no local repository used when resolving dependencies  though your installed artifacts do still get put in the default location    When I d replaced that with  lt localRepository gt   user home   m2 repository lt  localRepository gt  it started working   For  nix  that would be  lt localRepository gt   user home   m2 repository lt  localRepository gt   I suppose

User · Answer

Even in offline mode  maven will check remote repositories if there is a  remote repositories marker for the dependency  If you need to operate in offline mode  you may need to delete these files   The simple shell command below deletes these marker files  This is safe to do if you only use offline mode for the machine  I would NOT do this on a machine that needs to pull files down from the web   I have used this strategy on a build server that is disconnected from the web  We have to transfer the repository to it  delete the marker files and then run in offline mode   On Linux   Unix you can delete the remote repository marker files this way   cd    m2 find   -name   remote repositories  -type f -delete

User · Answer

Even I faced this issue and solved it with 2 ways   1  In your IDE select project and clean all projects then install all the maven dependencies by right clicking on project -  go to maven and Update project dependencies select all projects at once to install the same  Once this is done run the particular project  2   Else What you can do is check in the pom xml for the dependencies for which you are getting error and  mvn clean install  those dependent project first and the install maven dependencies of the current project in which you facing issue  By this the dependencies of the local project will be build and jars will be created

User · Answer

check if if your artifact Y have packaging set to  quot jar quot   If you have defined it as  quot war quot  by error or copy paste  it will show this strange  quot was cached in the local repository  resolution will not be reattempted until the update interval of internal has elapsed or updates are forced quot   I would expect something like  quot artifact Y is war  jar type expected quot

User · Answer

In my case I needed project Y to be a WAR to be deployed through Tomcat  as well as it needed to be a JAR to be able to add it as a dependency in project X  So in project Y s pom xml  I added this plugin to create a JAR along with the WAR               lt plugin gt                   lt artifactId gt maven-war-plugin lt  artifactId gt                   lt version gt 3 2 2 lt  version gt                   lt configuration gt                       lt attachClasses gt true lt  attachClasses gt                       lt classesClassifier gt classes lt  classesClassifier gt                   lt  configuration gt               lt  plugin gt   And while adding the dependency of project Y in project X s pom xml  I had to add a classifier           lt dependency gt               lt groupId gt groupId of project Y lt  groupId gt               lt artifactId gt project Y lt  artifactId gt               lt version gt 1 0-SNAPSHOT lt  version gt               lt classifier gt classes lt  classifier gt           lt  dependency gt   Note  when you build project Y  you will see 2 packagings in the target folder  project-Y war and project-Y-classes jar  so that s why while importing you are specifying the classes classifier to import the JAR and not the WAR

User · Answer

Catch all  When solutions mentioned here don t work happend in my case   simply delete all contents from   m2  folder directory  and do mvn clean install

User · Answer

This happened because I had http instead of https in this    lt repository gt       lt id gt jcenter lt  id gt       lt name gt jcenter-bintray lt  name gt       lt url gt https   jcenter bintray com lt  url gt   lt  repository gt

User · Answer

I run to the similar problem when my new project depend on oracle jdbc jar which I have installed in my local repository and work well for other projects   I tried -U option  deleting  lastupdate file or the whole directory and downlaod again but it did not work  finally I deleted the directory and installed it locally again it works

User · Answer

The local Maven repo tracks where artifacts originally came from using a file named   maven repositories  in the artifact directory  After removing it  the build worked  This answer fixed the problem for me

User · Answer

One of the errors I found around Maven is when I put my settings xml file in the wrong directory  It has to be in  m2 folder under your user home dir  Check to make sure that is in the right place  along with settings-security xml if you are using that

User · Answer

If you have  lt repositories  gt  defined in your pom xml apparently your local repository is ignored

User · Answer

Maven remembers when it didn t find something  The key is  resolution will not be reattempted until the update interval of internal has elapsed or updates are forced -    The quick solution is to delete your local  repository  subdirectory for the problem artifact - assuming you have fixed the problem with it      mvn -U will force update from remote repository - again  assuming you have now populated remote with said artifact

User · Answer

As the options here didn t work for me  I m sharing how I solved it   My project has a parent project  with its own pom xml  that has many children modules  one of which  A  has a dependency to another child  B   When I tried mvn package in A  it didn t work because B could not be resolved   Executing mvn install in the parent directory did the job  After that  I could do mvn package inside of A and only then it could find B

User · Answer

I had the same error from a different cause  I d created a starter POM containing our  good practice  dependencies  and built  amp  installed it locally to test it   I could  see  it in the repo  but a project that used it got the above error   What I d done was set the starter POM to pom  so there was no JAR   Maven was quite correct that it wasn t in Nexus -- but I wasn t expecting it to be  so the error was  ummm  unhelpful   Changing the starter POM to normal packaging  amp  reinstalling fixed the issue

[maven] Maven fails to find local artifact

Examples related to maven

Examples related to dependency-resolution