[BUILD-179] Enforce setting versions on plugins Created: 22/Oct/14  Updated: 13/Apr/17  Resolved: 23/Oct/14

Status: Closed
Project: Build
Component/s: None
Affects Version/s: None
Fix Version/s: POMs 30

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to BUILD-165 Specify all versions of Maven plugins... Closed
is related to BUILD-169 Update maven-enforcer-plugin to 1.3.1 Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

It is good practice to specify Maven plugins version explicitly. Since Maven 3, warnings are output when versions aren't specified. With BUILD-165, we've added a bunch a version, and since BUILD-169, we can enforce they're specified. Let's do this by adding the <requirePluginVersions> rule.

Worth noting for anyone stumbling upon this, or trying to test it:

  • The enforcer plugin is bound to the validate phase of the default lifecycle.
  • The clean lifecycle does not execute the validate phase
  • Which means that mvn clean will not show up enforcer problems

Generated at Sun Feb 11 23:39:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.