-
Task
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
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)
- is depended upon by
-
BUILD-183 Set installAtEnd to true for maven-install-plugin
- Closed
- is related to
-
BUILD-153 Update dependency plugin to 2.9.2
- Closed
-
BUILD-211 When running Clover, compiler still generates code twice, leading to duplicate classes
- Closed
-
BUILD-179 Enforce setting versions on plugins
- Closed
-
BUILD-135 Update site plugin to 3.4
- Closed
-
BUILD-170 Update build-helper-plugin to 1.9.1
- Closed