Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343835 - org.eclipse.m2e:lifecycle-mapping should work in parent
Summary: org.eclipse.m2e:lifecycle-mapping should work in parent
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-26 08:34 EDT by benson margulies CLA
Modified: 2021-04-19 13:25 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description benson margulies CLA 2011-04-26 08:34:35 EDT
Build Identifier: I20110310-1119

I've got an aggregate project with many eclipse plugins, and each of inherits org.sonatype.tycho:maven-osgi-source-plugin from the parent. However, m2e is insisting that I put the 'ignore' pseudo-plugin configuration in every single POM. This is with current 0.13 milestone.

Reproducible: Always

Steps to Reproduce:
Just see details.
Comment 1 Milos Kleint CLA 2011-04-26 08:44:05 EDT
does the infrastucture really insist on current pom locationor the quickfix just merely generates the pom snippet into the current pom only? 
I was under impression that the pom snippet is fully inheritable and can be freely copy&pasted to a parent of choice.
Comment 2 benson margulies CLA 2011-04-26 08:47:07 EDT
I tried adding it to the parent and Eclipse continued to red-x and generally harass me until I added it to the children, even after running 'update product configuration'.
Comment 3 Milos Kleint CLA 2011-04-27 04:54:08 EDT
in the latest HEAD (built from sources), the editor quickfix allows me to select the parent pom and directly add the configuration snippet there. When I do so, errors disappear in multiple projects, on undo they automatically reappear. I got either fixed or there is something different in your setup.

Please double check that the parent file where you write the configuration is indeed used in the effective pom. Sometimes when <relativePath> is missing or wrong, or the parent versions don't match, a different pom file (from local/remote repository) is used instead of the one in your source code.
Comment 4 benson margulies CLA 2011-04-28 19:22:32 EDT
If it's fixed at the head, it's fixed at the head. It definitely does not offer to fix the parent in the latest 0.13 milestone I installed.
Comment 5 Igor Fedorenko CLA 2011-05-09 11:04:28 EDT
Closing as WORKSFORME based on previous comments
Comment 6 Denis Roy CLA 2021-04-19 13:25:25 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/