Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
3.2.1
-
None
-
None
Description
The rule fails if a plugin is configured in 2 pluginManagement sections (one of which is in a profile), and the profile's pluginManagement does not configure a plugin version.
Profiles are often used to augment the existing configuration for a plugin, so there's no need to repeat the version number.
However if the profile is introducing the plugin to the build, then a version tag should be required.
The rule should evaluate whether a version number has been set after aggregating the configurations and resolving the profiles.
This is a new issue from Maven 4.0.0-alpha-5