[MENFORCER-321] RequirePluginVersions check works wrong on multi-module projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M2
• Fix Version/s: 3.0.0-M3
• Component/s: Standard Rules
• Assignee: Karl Heinz Marbaise
• Reporter: Alex Shesterov
• Created: 05/Oct/18 14:38
• Updated: 24/Feb/19 23:41
• Resolved: 24/Feb/19 23:41

Description

The RequirePluginVersions check doesn't work as documented on multi-module projects:

 

1. When the build is started on the parent POM:
If plugin versions are defined for just one of the modules (not the parent), the check succeeds, even if the plugin versions aren't defined for the parent pom or some other modules.

For example, the <requirePluginVersions> check succeeds for the following structure, if mvn validate is run for the parent POM: 

Parent POM: does NOT define plugin versions, modules: Sub1, Sub2.
  |_ Sub1: Defines plugin versions.
  |_ Sub2: Does NOT define plugin versions. 

 

 

2. When the build is started for a "child module" which inherits plugin versions from its parent, the enforcer plugin reports a failure.

For example, the <requirePluginVersions> check fails for the following structure, if mvn validate is run for Sub1: 

Parent POM: Defines plugin versions, modules: Sub1, Sub2.
  |_ Sub1: Inherits plugin versions.
  |_ Sub2: Inherits plugin versions. 

 

 

Issue Links

• is duplicated by: MENFORCER-306 [REGRESSION] RequirePluginVersions fails
• is part of: MENFORCER-306 [REGRESSION] RequirePluginVersions fails