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

Bug 337990

Summary:	wrong originating location for multiple executions of single plugin
Product:	z_Archived	Reporter:	Milos Kleint <mkleint>
Component:	m2e	Assignee:	Paul Tatavu <vladt>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	vladt
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Milos Kleint

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 1 Paul Tatavu

2011-02-24 14:16:53 EST

Fixed:
http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=35c9f9568763fe19eeecf27c90da467093ff02d5
https://github.com/sonatype/m2e-core-tests/commit/11da9571a24fb027010ea8fdb6aff4c8e3c2c608

Comment 2 Denis Roy

2021-04-19 13:22:59 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/