Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350466 - no error marker for misplaced <pluginManagement/> element
Summary: no error marker for misplaced <pluginManagement/> element
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-27 11:59 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:25 EDT (History)
1 user (show)

See Also:

Attachments
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 Igor Fedorenko CLA 2011-06-27 11:59:52 EDT 
Found this while investigating http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00874.html . For some reason, m2e does not create error marker for wrong pom.xml markup.
Comment 1 Milos Kleint CLA 2011-06-27 12:05:14 EDT 
my wild guess is that it's because the MavenProject is loaded with no validation whatsoever so we get no errors back from maven backend. I think there was an issue filed for it (with regard to some other errors maven itself complains about but we never show in the editor) but I cannot find it now..
Comment 2 Igor Fedorenko CLA 2013-09-28 23:43:46 EDT 
closing old/stale bugreports
Comment 3 Denis Roy CLA 2021-04-19 13:25:25 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/