Specify highest/lowest version for maven dependency

Question

Using the following versioning logic

major.minor.build

is there any way to specify that my project depends on a specific major version, the highest minor and the lowest build number?

I need to do this because I'm using the maven-dependency-plugin to copy all the dependencies of our multiple WAR files into a common folder, so that it can be sent to the client the latest version, but at the same time keep the numbers of packages to a minimum.

Look here : http://stackoverflow.com/questions/30571/how-do-i-tell-maven-to-use-the-latest-version-of-a-dependency — user2073100, May 28 '15 at 15:17
I had already looked into that, but that doesn't explain how to use the lowest available. — Gonçalo Cardoso, May 28 '15 at 15:32
Take a deep look at the maven-assembly-plugin would be easier and you can create a zip/tar.gz archive from it... — khmarbaise, May 29 '15 at 06:09

score 1 · Answer 1 · answered Jun 01 '15 at 17:20

No, it is not possible. When Maven encounters multiple matches for a version reference, it uses the highest matching version. Here you can find good explanation how to work with version ranges in maven.

I can suggest other solution for your original task:

Create new maven module.
Add all projects that you need as a dependencies to this module.
Use maven-dependency-plugin to copy dependencies of this module.

Maven guarantees that one and only one version of each (groupId:artifactId) is used. You can check resolved versions using mvn dependency:tree.

Specify highest/lowest version for maven dependency

major.minor.build

1 Answers1