[BUILD-165] Specify all versions of Maven plugins in super pom Created: 20/Oct/14  Updated: 13/Apr/17  Resolved: 22/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:
dependency
is depended upon by BUILD-183 Set installAtEnd to true for maven-in... Closed
relation
is related to BUILD-153 Update dependency plugin to 2.9.2 Closed
is related to BUILD-211 When running Clover, compiler still g... Closed
is related to BUILD-179 Enforce setting versions on plugins Closed
is related to BUILD-135 Update site plugin to 3.4 Closed
is related to BUILD-170 Update build-helper-plugin to 1.9.1 Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

Maven's default behavior is to pickup latest found version of plugins, if no specific version is requested by the pom. Since Maven 3, Maven outputs warnings when plugins are used without a specific version; it's considered good practice to specify all versions of all plugins, since that leads to better/more reproducible builds.

Since our builds were currently not relying on specific versions of these plugin, this issue is to be considered a "meta" one that covers several plugin updates (we generally have on jira ticket for each plugin for the sake of the changelog)

We should fix those:

  • clean: 2.6
  • install: 2.5.2 (provides installAtEnd, skip, ...)
  • resources : 2.7
  • jar : 2.5
  • compiler : 3.2
  • dependency : 2.9 (BUILD-153)
  • enforcer : 1.3.1 (BUILD-169)

This will also imply removing some version tags: for reports, if the plugin is already in the plugins section, the version is not necessary (since BUILD-135)


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