[ http://jira.codehaus.org/browse/MNGECLIPSE-203?page=comments#action_78791 ] Eugene Kuleshov commented on MNGECLIPSE-203: --------------------------------------------
I am sorry, but you would have to provide more details. Ideally provide example project that would allow to reproduce this issue. Otherwise I can only suggest you to debug trough it in your own environment. > Maven Eclipse Plugin fails to read POM while command line works > --------------------------------------------------------------- > > Key: MNGECLIPSE-203 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-203 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Components: Dependency Resolver > Affects Versions: 0.0.10 > Reporter: Yuri Schimke > > I have got this error a couple of times in eclipse, but things are working > well in the command line. > To fix it I tried deleting and reverting the mentioned POM files, but in the > end restarting eclipse was the only thing to fix it. > Severity and Description Path Resource Location > Creation Time Id > Unable to get dependency information: Unable to read the metadata file for > artifact 'XXX:etl:jar': Cannot find parent: XXX:XXX-MODULES for project: > XXX:XXXServer:pom:1.2.1-SNAPSHOT > XXX:etl:jar:1.2.1-SNAPSHOT > from the specified remote repositories: > Maven Snapshots (http://snapshots.maven.codehaus.org/), > central (http://ibiblio.org/maven2), > internal-snapshot (XXX), > internal-3rdparty (XXX), > internal-released (XXX), > mergere (http://repo.mergere.com/maven2) > Path to dependency: > 1) XXX:data_server:jar:1.2.1-SNAPSHOT > XXX Data Server pom.xml line 1 1161087949549 186247 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
