Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345484 - Resolution of local projects with pom packaging is broken
Summary: Resolution of local projects with pom packaging is broken
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-11 14:22 EDT by Eugen Paraschiv CLA
Modified: 2021-04-19 13:26 EDT (History)
1 user (show)

See Also:

Attachments
2 projects for reproducing the issue (23.24 KB, application/zip)
2011-05-11 14:24 EDT, Eugen Paraschiv CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eugen Paraschiv CLA 2011-05-11 14:22:51 EDT 
Build Identifier: 

I'm running into a problem with my current maven projects. I have a few projects with pom packaging, used only to define some dependencies. m2eclipse was resolving everything just fine until recently. Now, I'm encountering several problems - first, for all these projects of type pom, I'm getting: 

5/11/11 1:18:14 AM EEST: [WARN] The POM for org:commons-spring:pom:0.0.3-SNAPSHOT is missing, no dependency information available
5/11/11 1:18:14 AM EEST: Missing artifact org:commons-spring:pom:0.0.3-SNAPSHOT:compile

I have also created 2 sample projects (attached to this bug report) to exemplify the issue, but I'm seeing yet another problem with these as well: 
Project build error: Non-resolvable parent POM: Could not find artifact org:commons-server:pom:0.0.3-SNAPSHOT and 'parent.relativePath' points at wrong local POM

The command line build works fine. I'm using the most recent stable version of m2e (0.12.1) on a Eclipse 3.6.2 (EE). 
Any help is appreciated. 
Thanks. 

Reproducible: Always
Comment 1 Eugen Paraschiv CLA 2011-05-11 14:24:06 EDT 
Created attachment 195406 [details]
2 projects for reproducing the issue
Comment 2 Igor Fedorenko CLA 2011-05-11 21:08:06 EDT 
I am unable to reproduce the problem with a recent m2e 0.13. all five projects are successfully imported in workspace  and have no dependency or parent resolution errors.
Comment 3 Denis Roy CLA 2021-04-19 13:26:43 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/