Update: the repository pollution protection feature introduced in Clover-for-Maven 4.0.4 can partially protect against multiple classifiers (CLOV-1632).

Switching from clover2:instrument to clover2:setup works for my situation because it avoids installing the artifacts to the local repo. Thanks for your help.

Hi Thomas,

Maven doesn't support doubly classified artifacts.

You can use clover2:setup however, instead of clover2:instrument.
clover2:setup will not add the clover classifier, so it should work with classified artifacts.

ie: clover2:setup test clover2:clover.

Cheers,
Nick

So, just to be clear, Clover does not and will not support artifacts that have a classifier?

Unfortunately, Maven does not support artifacts that have multiple classifiers.
In this case, there is a -test classifier on the artifact, and then Clover adds its own -clover classifier.

If the <Target_Path>\my-artifact-1.0.0-SNAPSHOT-tests.jar, were not a classified artifact, then this problem would not exist.

The work around is to put any tests that need to be shared across projects (ie installed) in a separate module, and not have maven use a -classifier on them.
Before doing this however, you should consider the need to install a -test.jar into a maven repository at all.

If you can use the tests that are already compiled in the reactor, this issue should also go away. One way to do this is to use the dependency:unpack-dependencies goal, on the maven-dependency-plugin. It will copy a dependency from the maven reactor to a given location. If it is not in the reactor, then the dependency is looked for in a repository. The same goes for copy-dependencies.

Another solution is to tell Clover to not instrument your test sources. This will mean however that no test results nor per-test coverage will be available in the Clover HTML reports. This can be set using the includeTestSourceRoots configuration.

Is a fix in the work for this? I too have been affected by this issue.