Eclipse Dependency Hierarchy Project Read Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might could not read maven project eclipse have Meta Discuss the workings and policies of this site About
Could Not Read Pom Xml Eclipse
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads
Artifact Descriptor Exception Failed To Read
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million
Maven Import Could Not Read Pom Xml
programmers, just like you, helping each other. Join them; it only takes a minute: Sign up m2e gives inscrutable “project read error” up vote 10 down vote favorite 1 I just started to use m2e to try to build the sample travellog elastic beanstalk project. On the console I'm getting "[ERROR] Project read error". This org.eclipse.m2e.logback.appender unable to configure also appears in red on the "Dependency Hierarchy" tab. What does this mean and how do I find out more details? Edit: Adding pom.xml
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack failed to read artifact descriptor Overflow the company Business Learn more about hiring developers or posting ads with us plugin execution not covered by lifecycle configuration Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a maven eclipse plugin community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up question about maven dependency up vote 2 down vote favorite 1 i loaded the maven project http://stackoverflow.com/questions/10788023/m2e-gives-inscrutable-project-read-error in eclipse then found sth wrong with pom.xml file, when i clicked the 'overview' tab(m2eclipse), it said: Failed to read artifact descriptor for commons-logging:commons-logging:jar:1.1.2-SNAPSHOT when i clicked the dependency hierarchy tab, it showed 'Project read error', however i have no problem to run 'mvn dependency:tree' from command line and can see there is a dependency on commons-logging: commons-logging:commons-logging:jar:1.1.1:compile just don't understand where the commons-logging 1.1.2-SNAPSHOT comes from. any idea ? Thanks. http://stackoverflow.com/questions/7019648/question-about-maven-dependency maven dependencies share|improve this question asked Aug 11 '11 at 0:49 ohana 1313 add a comment| 3 Answers 3 active oldest votes up vote 0 down vote accepted eclipse by default does not use the same maven installation as your command line. Depending on your m2eclipse version it might use an embedded maven snaphsot (with strange behaviour). Check eclipse -> Window -> Preferences -> Maven -> Installations and add your external maven installation (prefer current version 3.0.3) to the list and use this as default. share|improve this answer answered Aug 11 '11 at 11:12 FrVaBe 24.2k86899 add a comment| up vote 1 down vote In order to determine where the dependency commons-logging comes from (even without the .pom editor and its dependency editor) open the console and execute the following command: mvn dependency:tree -Dverbose -Dincludes=commons-logging This will show all dependencies of commons-logging. I looked through the dependency tree, but did not find any reference to 1.1.2-SNAPSHOT. Finally, adding the following dependency to my pom.xml solved the problem:
Things LocationTech Long-Term Support PolarSys Science OpenMDM More Community Marketplace Events Planet Eclipse Newsletter Videos Participate Report a Bug Forums Mailing Lists https://www.eclipse.org/forums/index.php/t/230370/ Wiki IRC How to Contribute Working Groups Automotive Internet of Things LocationTech Long-Term Support PolarSys Science OpenMDM Toggle navigation Home Projects Forums Eclipse Community Forums Forum Search: Search Help Register Login Home Home» Archived» Maven Integration (M2E)» pom file shows missing artifact errors(My imported project seems to fine except could not eclipse (Indigo 3.7) is showing errors for missing artifacts ) Show: Today's Messages :: Show Polls :: Message Navigator pom file shows missing artifact errors [message #709403] Wed, 03 August 2011 22:12 Ara BulbulianMessages: 2Registered: August 2011 Junior Member using Indigo 3.7 (m2e integrated in) I would think this would be something simple could not read to fix, but I can't seem to understand why Eclipse can't find the artifacts (all listed as missing) listed in my POM file. So I have a long list of errors in my Eclipse 'Problems' tab and my POM.xml I was able to run mvn commands from the command line just fine and all the dependencies were created in my /.m2/repository/ dir. What is it that eclipse is using to try and validate my pom.xml? Very annoying that even the error messages are almost meaningless. All are 'Missing artifacts...' and are on line 1 of my pom.xml? Other developers using eclipse 3.4 and even 3.7 (Pulse build) don't seem to have my same issue. A few things I already checked: 1) eclipse -> preferences -> maven -> installation: Embedded 3.0.2 2) eclipse -> preferences -> maven -> user settings: local repository looks correct 3) eclipse -> preferences -> java -> build path -> classpath variables: