Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 336410 - Allow mapping of mojo executions from non-default lifecycles
Summary: Allow mapping of mojo executions from non-default lifecycles
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-04 21:42 EST by Igor Fedorenko CLA
Modified: 2021-04-19 13:27 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-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 CLA 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 CLA 2011-02-28 15:00:37 EST 
Verified
Comment 3 Denis Roy CLA 2021-04-19 13:27:11 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/