Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338317 - Do not create error markers for projects with unmapped packaging types
Summary: Do not create error markers for projects with unmapped packaging types
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-26 18:10 EST by Igor Fedorenko CLA
Modified: 2021-04-19 13:22 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-02-26 18:10:21 EST 
With implementation of bug 337010, it is no longer necessary to provide explicit lifecycle mapping metadata for each packaging type. DefaultLifecycleMapping provides good/desired behaviour in all but few special cases, like m2eclipse-tycho projects. Because of this, m2e should not create error markers for projects without explicit lifecycle mapping for packaging type. m2e should still create error markers for not-covered interesting plugin executions and when configured project lifecycle mapping strategy cannot be instantiated for whatever reason.
Comment 2 Paul Tatavu CLA 2011-02-28 14:34:33 EST 
Verified
Comment 3 Denis Roy CLA 2021-04-19 13:22:02 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/