Maven Failed to read artifact descriptor

Question

I am hoping someone can help me with a problem I am struggling with   When I try to build my project from the terminal I get this error   Failed to read artifact descriptor for com morrislgn merchandising common test-data-utils jar 0 3b-SNAPSHOT  Could not find artifact com morrislgn merchandising merchandising pom 0 3b-SNAPSHOT   The common test-data-utils jar is created by a separate project and shared between this and another project  the other project doesn t build either  but that is down to another problem     I am able to build com morrislgn merchandising common test-data-utils without issue  I can see the entry it makes in the  m2 local repository on my machine  I have reindexed my repository in Eclipse also    The POM for my project has this entry    lt dependency gt       lt groupId gt com morrislgn merchandising common lt  groupId gt       lt artifactId gt test-data-utils lt  artifactId gt       lt version gt 0 3b-SNAPSHOT lt  version gt   lt  dependency gt    Which appears to be correct to me - the POM doesn t report any errors either when it is viewed in Eclipse   Can some one tell me what I am missing here or doing wrong

User · Answer

If you re using eclipse   right click on project -  properties -  Maven  and make sure that the  Resolve dependencies from workspace projects  is not clicked   Hope this helps

User · Answer

I had a similar problem   In my case  the version of testng in my  m2 repositories folder was corrupt  but when I deleted it  amp  did a maven update again  everything worked fine

User · Answer

I had the same problem for a while and despite doing mvn -U clean install the problem was not getting solved   I finally solved the problem by deleting the whole  m2 folder and then restarted my IDE and the problem was gone   So sometimes the problem would rise because of some incompatibilities or problems in your local maven repository

User · Answer

Reference  Maven error  quot Failure to transfer    quot   find    m2  -name    lastUpdated  -exec grep -q  Could not transfer        -print -exec rm

User · Answer

You can always try mvn -U clean install  -U forces a check for updated releases and snapshots on remote repositories

User · Answer

I had same problem using IntelliJ  I solved with right click on pom xml   Maven   Reimport

User · Answer

I just started using STS Eclipse with first time using Maven  The project I setup already had its own settings xml  If this is the case  you ll want to update your settings xml file in run configuration    right click the pom xml and  Run As  -   Run Configurations     where it says  User settings  click on the File button and add the settings xml  I think this is specific to your project but my  Goals  is set to  clean install  and I checked on  Skip Tests

User · Answer

You mention two different groupIds  com morrislgn merchandising common and com johnlewis jec webpim common  Maybe this is the problem

User · Answer

I have a project    A    --a1   --a2   Now there is another project in our org   B    --b1   --b2   --b3    Every module a1  b1 etc  and Parent projects A  B have their own pom xml as per standard maven rules of parent and child   Both projects are checked out on my local eclipse  from SVN   I am actively working on A    I came to know that there is a good common functionality  b4  developed in B and I needed to use it     B    --b1   --b2   --b3   --b4  NEW    Developer of b4 have deployed this b4 module as an artifact in our org s repository  I included the dependancy to my module s POM i e  a2 s pom xml  Eclipse downloaded the reuqired artifact from repo and I could import the classes in it   Now issue starts    I needed to check the source code of b4 for some purpose and as I already had B checked out on my local eclipse I updated it from SVN and checked out module b4  I also ran pom xml of module b4 with targets like clean  package etc  After some time when I finishedd my coding I needed to create a JAR of my module a2  I ran  package  on a2 s pom xml and BAM   errors n errors for a2 module   These errors were also not very user friendly  Only thing is there was b4 s name for sure in logs   Solution  After trying for many solutions for many hours  I ran  mvn -U clean install  from console in my B s  project directoty  i e  in    codebase B   As B is the parent  clean install command ran for all modules including b4 and it ran successfully  After this I ran  mvn -U clean install  for my parent project which is A  And this worked  a2 module got compiled  installed   packaged later  succesfully   Here important point was if b4 is in your workspace do not only install b4  You will need to clean-install complete B  I came up to this solution after reading answer from Zuill  EDIT  One more thing here to note that if I didn t had B project checked out in Local environment then this issue might not have occurred for me  I tend to think that this happened cause I had B checked out in my local workspace

User · Answer

This error is basically saying that maven couldn t read a certain dependency from local repository  It might happend because a jar file didn t get downloaded correctly  So  go to your maven local repository and make sure there isn t any  lastUpdated extension file

User · Answer

Failed to read artifact descriptor  problems generally indicate a problem with the dependency s pom file in the maven repository  I would suggest you to double check if the pom file s name is the same with the name maven expects  and also to check if the pom file contents are valid

User · Answer

I know I m brave  nine years after the question    For me it was a problem where sub-dependencies weren t found  I finally found the real issue by looking at the  quot Error Log quot -view that held a An internal error occurred during   quot Building quot  -line  Double-clicking it showed a pop-up with a stacktrace and the last cause finally disclosed a broken JAR in my local repository  I cleaned that up and Eclipse m2e was able to work again

User · Answer

Navigate via shell inside of your project folder and run following command    mvn -U clean install   Usually this should already solve your problem   If you see a message like this      Could not resolve dependencies for project  war 0 0 1-SNAPSHOT  Failed to collect dependencies at com sun jersey jersey-server jar 1 9   Then execute   export MAVEN OPTS -Dhttps protocols TLSv1 TLSv1 1 TLSv1 2   followed by   mvn -U clean install   again to finally update your dependencies    Afterwards perform clean maven build    maven clean install

User · Answer

In our case the error appeared because of the incorrect groupId renaming while some of the projects in multi-module Maven configuration references to others   We had an aggregator project  billing-parent  with two modules  billing-api  billing    com company team billing-parent  -com company team billing-api  -com company team billing   Project billing depends on billing-api  So in its pom xml it had    lt dependency gt       lt groupId gt com company team lt  groupId gt       lt artifactId gt billing-api lt  artifactId gt       lt version gt   project version  lt  version gt   lt  dependency gt    We decided to rename groupId from com company team to com company team billing  We replaced old value in parent s pom xml and in  lt parent gt  sections of both modules  But forgot to update dependency above  So we had got configuration in which billing project references old billing-api artifact  Eventually it beaks build of the billing module after some time with the error like   ERROR  Failed to execute goal on project billing  Could not resolve dependencies for project com company team billing billing jar 3 5 1-SNAPSHOT  Failed to collect dependencies at com company team billing-api jar 3 5 1-SNAPSHOT  Failed to read artifact descriptor for com company team billing-api jar 3 5 1-SNAPSHOT  Failure to find  lt parent of the com company team billing-parent project which is not available any more gt       despite the fact that billing-api module builds without errors   Solution 1  rename groupId in dependency as well   Solution 2  replace groupId by the   project groupId  property like this    lt dependency gt       lt groupId gt   project groupId  lt  groupId gt       lt artifactId gt billing-api lt  artifactId gt       lt version gt   project version  lt  version gt   lt  dependency gt    Conclusion  So my advice in case you encountered with the error in multi-module configuration whould be  thoroughly check groupId and artifactId of the dependencies on neighbour modules

User · Answer

If you are using Eclipse  Right Click on your Project -  Maven -  Update Project  It will open Update Maven Project dialog box    In that dialog box  check Force Update of Snapshots Releases checkbox  amp  click OK   Please refer image below     This worked for me

User · Answer

I solved this problem by  changing the maven setting xml and repository

User · Answer

For me  it seems to actually have been a problem with the dependency POM   I worked around it by using the jitpack virtual repository  with which you can include github repositories based on their URL instead of their own POM  which seems to have been erroneous in my case         lt repository gt           lt id gt jitpack io lt  id gt           lt url gt https   jitpack io lt  url gt       lt  repository gt

User · Answer

I had the same issue with eclipse where the maven build command line worked just fine BUT  try this   go into  m2 repository and wipe the directory associated run update maven dependencies in eclipse   The error goes away    why my mvn command line worked with those directories and eclipse  m2eclipse could not  I have no idea and it kinda sucks   My project is now working in eclipse again

User · Answer

This helped me   From the IDE  Red Hat CodeReady Studio in my case    Windows -  Show View -  Terminal -  Open Add local terminal  Run commands as follows       cd  pom-file-path     mvn -U clean install

User · Answer

I had this problem in eclipse  mvn -U clean install didn t work but right clicking the project and selecting Maven- Update Project fixed it

User · Answer

Did not have any luck updating via eclipse  Had to use mvn clean install -U  which resolved everything

User · Answer

I know I m pretty late to the conversation  but I had this problem too  I think the issue was my company s firewall  My solution was to unplug from the network  connect to our open wireless and then force an update via Eclipse  This resolved everything

User · Answer

Had the same issue with IntelliJ IDEA and following worked     Go to File Select Settings Select Build  Execution  Deployments Select Build Tools from drop down Select Maven from drop down Tick the Always update snapshots check box

User · Answer

For me   it was related to setting the  User Setting xml  inside   Window  gt  preferences  gt  Maven  gt  User Settings  gt  and then browsing to the user Settings inside the   maven unarchived directory     apache-maven-2 2 1 conf settings xml

User · Answer

This problem can occur if you have some child projects that refer to a parent pom and you have not installed from the parent pom directory  run mvn install from the parent directory   One of the child projects may depend on a sibling project and when it goes to read the pom of the sibling  it will fail with the error mentioned in the question unless you have installed from the parent pom directory at least once   I just ran into this problem when moving a project to a new computer  I was in the habit of running commands from the child project and didn t run install on the parent

User · Answer

I solved this issue by deleting in the repository folders where this error was shown everything except the  jar and  pom files

[java] Maven: Failed to read artifact descriptor

Examples related to java

Examples related to maven

Examples related to dependencies