Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345404

Summary: A missing pom for a dependency causes an error for system dependency
Product: z_Archived Reporter: Kristof Vanbecelaere <kristof.vanbecelaere>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: igor
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Small pom showing the problem described. none

Description Kristof Vanbecelaere CLA 2011-05-11 07:50:02 EDT 
If a pom includes a system dependency and an existing dependency with a missing pom (so jar exists in repo, pom does not) then m2e (0.12.0) complains about not being able to resolve the system dependency. See enclosed pom. In my case the jar for springmodules:springmodules-cache:0.9 is present in my repo.
Comment 1 Kristof Vanbecelaere CLA 2011-05-11 07:51:05 EDT 
Created attachment 195332 [details]
Small pom showing the problem described.
Comment 2 Igor Fedorenko CLA 2011-05-11 21:13:59 EDT 
I am not able to reproduce the problem with a recent 0.13 build. Attached sample project imports successfully and both springmodules-cache and com.sun:tools are resolved as expected.
Comment 3 Kristof Vanbecelaere CLA 2011-05-13 03:35:53 EDT 
I installed a recent 0.13 build on Indigo M7. I found out what is causing this. If settings.xml contains a reference to a legacy repository the error manifests itself.
Comment 4 Kristof Vanbecelaere CLA 2011-05-13 03:46:08 EDT 
Actually, it was a reference to a legacy repository that recently got removed from the nexus I am connecting to. Removing the reference from my settings.xml solved the issue.
Comment 5 Denis Roy CLA 2021-04-19 13:23:58 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/