Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338539 - Quickfix to address mojo execution issue in the parent
Summary: Quickfix to address mojo execution issue in the parent
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: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-01 09:47 EST by Pascal Rapicault 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 Pascal Rapicault CLA 2011-03-01 09:47:59 EST 
When a plugin execution is flagged in a child but the plugin declaration is in the parent, I'm thinking that it could actually be useful to have a way to fix the problem in where the plugin execution is declared.
Comment 1 Milos Kleint CLA 2011-07-20 02:07:14 EDT 
I think we have this covered by the quickfix now (as it prompts user where to store the configuration, showing current pom and all it's workspace parents).

closing as fixed, please reopen if you disagree or I misunderstood the issue
Comment 2 Denis Roy CLA 2021-04-19 13:27:05 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/