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

Bug 336410

Summary:	Allow mapping of mojo executions from non-default lifecycles
Product:	z_Archived	Reporter:	Igor Fedorenko <igor>
Component:	m2e	Assignee:	Igor Fedorenko <igor>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	vladt
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Igor Fedorenko

2011-02-04 21:42:01 EST

As discussed on m2e-dev mailing list, some m2e extensions need ability to activate project configurators based on mojo executions from non-default lifecycle. Currently, only "site" is required, but I would also add "clean" just to cover all standard lifecycles.

Comment 1 Igor Fedorenko

2011-02-05 00:12:54 EST

Implemented. It is now possible to map mojo executions project configurators. 

Only default lifecycle is ever considered for execution inside workspace, this means that configurator's getBuildParticipant will never be called for mojo executions bound to non-default lifecycles. Likewise, mapping of such mojo executions to <execute/> action will be silently ignored.

http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=d132f15df7ad0e0d6f475e331bcc07bdcbb3070f


https://github.com/sonatype/m2e-core-tests/commit/57033dd61bb4337cbc5c6eba7d958c7920c8036e

Comment 2 Paul Tatavu

2011-02-28 15:00:37 EST

Verified

Comment 3 Denis Roy

2021-04-19 13:27:11 EDT

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