Maven versioning strategy

The maven-dependency-versions-check-plugin is a Maven plugin that verifies that strategy resolved versions of dependencies are mutually compatible with each other. The resolved version of every dependency declared explicitly in the current POM is the same or at least compatible with the one that was stated. For every explicitly declared dependency in the current POM, all its dependency versions are maven. Currently, the plugin is not in a public repository yet, so you'll have to build it yourself.

First clone the git repository and then simply do. This will install the plugin into your local repository and make it available for use. To make commandline usage a bit easier, you should add the com. This is the dependency list for the plugin itself. Every line contains of strategy following elements:.

These are the versions that were under versioning when choosing the final dependency. Running the check plugin will flag this as error and might fail the build.

These options are intended to be given on the command line. They can also be configured maven the config section see below but are less useful.

Transitive versions are still resolved and additional versions maven be listed. This goal checks all the dependencies, reports only problems and might fail the build if configured. It strategy intended to be run as part of the normal build cycle. In this case, it should be added like this:. The above sample shows a conflict with a dependency declared in the current POM. In this case, it will print.

The above will change to [ERROR] if the plugin is configured to fail the build in case of conflicts see below. Note also that any configuration in a POM overrides the default configuration e.

In rare cases you need to configure the plugin to make exceptions, i. For instance, in the above example you might insist that log4j version 1.

An exception is only for a specific version conflict, in this case 1. If the plugin finds that a different version of log4j was resolved or required, say 1. An exception must have all four elements groupId, artifactId, expectedVersion and resolvedVersion present. Boolean flag that enables warnings if a dependency that was excluded from version resolution depends on an incompatible version for historical reasons it is called 'warnIfMajorVersionIsHigher'.

Boolean flag that will turn warnings about dependency problems into error messages and fail the build accordingly. Defines a version strategy resolver. Version strategy resolvers are used to determine which strategy to apply to decide whether two versions are compatible with each other. Selects the default strategy to fall back on when no match is strategy in the resolvers configuration. Versioning, version numbers also carry semantic meaning e.

Apache APR versioning assigns indicators for forward- and backward-compatibility versioning each of the elements in a three-digit version versioning. To do so, it employs version resolving strategies. In the most simple use case, it uses the default strategy exclusively. It assumes that all smaller versions are compatible when replaced with larger numbers and compares version elements from left to right.

Three digit versioning, assumes that for maven versions to be compatible, the first digit must be identical, the middle digit indicates backwards compatibility i. All versions are backwards compatible. First digit must be the same or higher to be compatible i.

The version consists of a single number. Larger versions can replace smaller versions. The version number may contain additional letters or prefixes i.

A custom strategy must implement the com. Strategy interface and must declare itself as a plexus component. A jar containing a custom strategy can then used as a custom dependency of the plugin:. See the source code to the plugin and the existing strategies for examples on how to write strategies.

In general, you should try to upgrade dependency versions if you can make sure that they work e. If you cannot do that, then either add exclusions or add an explicit dependency in the current POM. If maven this fails, then add an exception configuration, but please use this only as a last resort. In this case you should add comments to the exceptions, exclusions or explicit dependencies that state why you added them e.

Consider four projects, A through D. A depends on B and C which both depend on D, but on different versions. B's and C's POM look like this:. Maven will resolve D's version to 1. This is obviously a problem since C needs at least version 1.

If we change A's POM to. However this is not a solution - imagine if B updates to version 1. In this case, Maven uses the version that is specified in A's POM and ignores both B and C. Still won't help in the case that B or C update to a newer version, though. This does not declare a dependency of ParentOfBAndC to D, but instead maven the version for all POMs that have this POM as a parent unless a version is stated in that POM.

Versioning and C then can be changed to this:. This versioning, B and C will get the same version. However if the version of D changes, both B and C will have to be released and A has to be updated to use both new versions, or we have the same problem again.

In some cases, we specifically don't want a transitive dependency. For instance, if in the above scenario we want to avoid version 1. This will have the effect of excluding the version of D that C brings to the party, so in our example it has the same strategy as adding an explicit dependency to A.

There are additional, subtle versioning when enforced versions strategy into play e. You should generally avoid enforcing versions this way. Code Issues 4 Pull requests 5 Projects 0 Insights Pulse Graphs. Maven plugin to find dependency version conflicts.

Clone or download Clone with HTTPS Use Git or checkout with SVN using the web URL. Open in Desktop Download ZIP. Latest commit ecf Sep 24, hgschmie [maven-release-plugin] prepare for next development iteration. More specifically, it will check that The resolved version of every dependency declared explicitly in the current POM is the same or at least compatible with the one that was stated.

The plugin can configured to issue warnings or fail the build in that case. How to get it Currently, the plugin is not in a public repository yet, so you'll have to build it yourself. First clone the git repository and then simply do mvn install This will install the plugin into your local repository and make it available for use.

Every line contains of the following elements: In this case, it should be added like this: In this case, it will print the expected version of the current POM the resolved version i. If the problem is instead between dependencies, then it will omit the expected version. POM configuration section Note also that any configuration in a POM overrides the default configuration e.

See below for more details on strategy resolvers. See below for more details on strategies. Strategies included with the plugin default - the default strategy This strategy is modelled after the actual maven version resolution. Writing your own strategies advanced usage A custom strategy must implement the com. A jar containing a custom strategy can then used as a custom dependency of the plugin: How to resolve conflicts Some more detailed explanation is below in the background section.

Maven 2's arbitrary version resolution strategy Consider four projects, A through D. B's and C's POM look like this: Use dependency management in the parent POM If B, maven C use a common parent POM, then the version of D can be specified in that parent POM: B and C then can be changed to this: Use exclusions In some cases, we specifically don't want a transitive dependency. Strategy Privacy Security Status Help. You can't perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.

Maven Tutorials 03 - How to use Maven 01 (Archetypes, GroupId, ArtifactId, Version, akowedananipa.web.fc2.com)