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

Bug 350203

Summary: Spurious warning about overriding the maven-release-plugin version
Product: z_Archived Reporter: Robert Munteanu <robert.munteanu>
Component: m2eAssignee: Milos Kleint <mkleint>
Status: RESOLVED FIXED QA Contact:
Severity: trivial    
Priority: P3 CC: mkleint
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=553839
Whiteboard:

Description Robert Munteanu CLA 2011-06-23 18:14:23 EDT 
The POM editor notifies me that I have overriden the version of the maven-release-plugin , but I have no parent POM ( other than the super-POM I guess ). IMO I have not overriden it, but declared it, the same as I did for e.g. the maven-compiler-plugin .

This warning if confusing and should not come up.
Comment 1 Robert Munteanu CLA 2011-06-24 07:24:34 EDT 
Same goes for the maven-assembly-plugin.
Comment 2 Milos Kleint CLA 2011-06-27 04:30:56 EDT 
confirmed. 
This behaviour is limited to maven-release-plugin, maven-dependency-plugin, maven-antrun-plugin and maven-assembly-plugin
When I enter "org.apache.maven.plugins" into the Add Plugin dialog, these show up as managed. Additionally the maven-deploy-plugin and maven-clean-plugin appear in gray, meaning they are being used in the project and again it's only used in the superpom.


I suppose the assumption of these being defined in the superpom is correct, however the superpom contains PM entries for other plugins that don't show up as managed.
Comment 4 Denis Roy CLA 2021-04-19 13:26:53 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/