This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes Ant, Maven and Other Build Tools and the fly likes Maven error sign wihout reason, Failed to collect dependencies Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Maven error sign wihout reason, Failed to collect dependencies" Watch "Maven error sign wihout reason, Failed to collect dependencies" New topic
Author

Maven error sign wihout reason, Failed to collect dependencies

Zoltaan Szabo
Greenhorn

Joined: Jul 01, 2013
Posts: 18
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
internet detective
Marshal

Joined: May 26, 2003
Posts: 29222
    
135

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?


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Zoltaan Szabo
Greenhorn

Joined: Jul 01, 2013
Posts: 18
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

Joined: Jul 01, 2013
Posts: 18
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

Joined: May 14, 2008
Posts: 5772
    
    7

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:




JBoss In Action
Zoltaan Szabo
Greenhorn

Joined: Jul 01, 2013
Posts: 18
Hi,
i have a <distributionManagement> section in the main project pom.xml:
Zoltaan Szabo
Greenhorn

Joined: Jul 01, 2013
Posts: 18
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
 
subject: Maven error sign wihout reason, Failed to collect dependencies
 
Similar Threads
linking my own application jar file to my maven build.
Maven error: Failed to collect dependencies
Maven project running problem
Error at the deploy webservice
Could not resolve dependencies for maven project