Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337990 - wrong originating location for multiple executions of single plugin
Summary: wrong originating location for multiple executions of single plugin
Status: RESOLVED FIXED
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: Paul Tatavu CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-23 10:58 EST by Milos Kleint 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 Milos Kleint CLA 2011-02-23 10:58:34 EST 
followup to 337220

found this error:
I have 2 definitions of  enforce plugin, each in different parent. I get 2 different error markers, but both hyperlinks (MARKER_CAUSE_RESOURCE_PATH, MARKER_CAUSE_LINE_NUMBER) only points to the one definition. (probably ignoring the execution definition.)

Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce (execution: enforce-maven, phase: validate)
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce (execution: default, phase: validate)

the project to reproduce is maven-hibernate3-components in mojo project.http://mojo.codehaus.org/source-repository.html
Comment 2 Denis Roy CLA 2021-04-19 13:22:59 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/