[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: |
|
||||||||||||||||||||||||||||||||
| 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:
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 |