Does Clover support Maven version ranges?

Q: My project uses Maven version ranges, e.g. [1.0.0,2.0.0). mvn clean install works, but the Clover build fails with:

setup failed for artifact com.abc:arti:null:jar.... The version can not be empty.

Version ranges are most likely not supported.

The reason is that Clover sometimes has to replace the original artifact with an instrumented one - the artifact having the clover classifier. Such a substitution requires a concrete version and cannot be expressed against a version range. This is why the version is reported as null in the error message above.

Workaround: declare explicit versions for dependencies of the modules being instrumented by Clover.

See also Warning about older clovered artifact version, which originates from the same artifact substitution mechanism, and How to remove -clover suffix from artifact name?.