java - Maven set dependency mediation strategy to newest rather than nearest

Question

Can I configure Maven to choose the "newest" dependency on a conflict, rather than the "nearest"?

The "newest" is the default in Ivy and other sensible dependency managers, see http://ant.apache.org/ivy/history/2.2.0/settings/conflict-managers.html

I find the "nearest" strategy is rarely what I want.

I'm using Maven 3.3.3, but I can switch versions if necessary.

I know how to override Maven's choice on individual conflicts, but I'd prefer to change the default so that I don't have to detect and fix each conflict one at a time.

(See the Maven docs on "Dependency mediation")

Answer 1

Can I configure Maven to automatically use the "newest" version of a dependency instead of the "nearest" when resolving version conflicts?

No, you cannot configure Maven's dependency mediation strategy to anything other than nearest.

Adding configurable dependency mediation strategies has been proposed before, but was ultimately abandoned because the proposal involved changing the POM XSD, which has not happened in years.

Why does Maven use the nearest strategy as a default?

The strategy of nearest is favored by Maven for two reasons:

1. Easy overriding of individual conflicts: For any particular conflicting dependency, you can specify its version within your own POM, and that version becomes the nearest.
2. Reproducible builds: Version ranges anywhere in your dependency graph can cause builds to not be reproducible. A mediation strategy of "newest" would magnify the negative impact of version ranges on build reproducibility.

But I really want a different dependency mediation strategy. What can I do?

These are your best options:

1. Make a Maven extension: Usage of the "nearest" strategy is specified by NearestVersionSelector in MavenRepositorySystemUtils. You could create your own Maven extension that defines your own VersionSelector that implements the strategy of your choice, then in the afterSessionStart method of your extension, replace the session's DependencyGraphTransformer with one that uses your custom VersionSelector.
2. Migrate to another build tool: Obviously.