Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0-alpha-4
-
None
Description
As reported by Sebastian Annies in Using a specific plugin version in custom lifecycle, the plugin version given by a lifecycle mapping like
<verify>org.apache.maven.plugins:maven-source-plugin:2.1:jar-no-fork</verify>
is not respected by Maven 3.0, it's preferring the version from the plugin management of the super POM instead.
Attachments
Issue Links
- is related to
-
MNG-6054 Remove super POM plugin management section
- Closed