File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Maven error sign wihout reason, Failed to collect dependencies

 
Zoltaan Szabo
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

The following problem happened: once i opened Eclipe, all the procects were signed with a red X. Opening the projet tree, there was no error sign in the nodes. Nothig showed me what caused the errors. I could not build the projects. Finally i created a new workspace for Eclipse, checked out the projects from SVN, imported them as Maven projects. (There were two main and several child projects.)
Ther are still two projects showing the red X but not showing what causes the errors. I have tried to refresh, clean in Eclipse. I cannot build the other projects without error either, of course also not the ones with errors. The error message is e.g.:

And for the erroneus project part of the message is:

Could please anyone help me to find a solution?
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 33696
316
Eclipse IDE Java VI Editor
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The first thing to try is to see if running Maven > update project configuration and Maven > update dependencies using the Maven Eclipse plugin to make sure you don't have stale metadata. Also, run > install to ensure you get the same error. I think you will, but it is good to rule those out.

The error message talks about two things. One is not finding the dependencies and the other is not being able to release. Since some of the dependencies are SNAPSHOTs, it doesn't make sense to be doing a release. Do you know why the project is using ext-release-local as the repository?
 
Zoltaan Szabo
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Thanks for your advice. I run Maven/update for all projects. I do not know how to update dependencies? I run clean compile. There was again a failure, with clean istall too.
How do you mean: "Since some of the dependencies are SNAPSHOTs, it doesn't make sense to be doing a release. Do you know why the project is using ext-release-local as the repository? "? Here are several projects in the workpace referencing other ones.
 
Zoltaan Szabo
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

All my Maven projects are snapshots. I do knot know why Maven wants to compile them to the release repository. How can i set it?
I also noticed that settings.xml under .m2 folder does not exist. Something really went wrong with Maven.
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There is no default settings.xml file in the .m2 directory, but you can always create one.

You can specify the remote repository for a "deploy" by adding a <distributionManagement> section to your pom.xml:



 
Zoltaan Szabo
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
i have a <distributionManagement> section in the main project pom.xml:
 
Zoltaan Szabo
Greenhorn
Posts: 18
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

My problem has resolved.
There was some problem with our repository. I deleted the reference to this. After that i was able to compile all projects.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic