I have no doubt that this was indeed a problem - however will close for now, until we can get reproduce this consistently.

Possibly an upgrade from maven 2.0.8 to maven 2.0.9 fixed this problem.

Well...after trying for about an hour the classpaths (clover/non-clover) match up.

My environment has changed a lot since I posted this so I don't know how it is miraculously fixed

Maybe David can provide an example.

Sorry.

Franz

Well...after trying for about an hour the classpaths (clover/non-clover) match up.

My environment has changed a lot since I posted this so I don't know how it is miraculously fixed

Maybe David can provide an example.

Sorry.

Franz

Nick -

I will generate this and send it off.

Thanks for helping.

Franz

Hi Franz,

After some further investigation - I can not reproduce the problem you are seeing.
I set up a sample project, which added org.apache.ant:ant:1.7.1 as a dependency excluding the ant-launcher artifact:

        <dependency>
            <groupId>org.apache.ant</groupId>
            <artifactId>ant</artifactId>
            <version>1.7.1</version>
            <exclusions>
                <exclusion>
                    <groupId>org.apache.ant</groupId>
                    <artifactId>ant-launcher</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

When I then run mvn clover2:instrument, the classPath for the maven-surefire-plugin (I also checked the maven-compiler-plugin) doesn't include ant-launcher.

[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.4.3:test' -->
[DEBUG]   (f) basedir = /work/mvnclvr/src/it/optmized/module-a
[DEBUG]   (f) childDelegation = false
[DEBUG]   (f) classesDirectory = /work/mvnclvr/src/it/optmized/module-a/target/clover/classes
[DEBUG]   (f) classpathElements = [/work/mvnclvr/src/it/optmized/module-a/target/clover/test-classes, /work/mvnclvr/src/it/optmized/module-a/target/clover/classes, /.m2/repository/com/cenqua/clover/clover/2.3.3-SNAPSHOT/clover-2.3.3-SNAPSHOT.jar, /.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar, /.m2/repository/org/apache/ant/ant/1.7.1/ant-1.7.1.jar]

Could you please provide the output when you run maven with the -X command and/or supply a small example pom.xml which will reproduce the problem you are having.

Best Regards,
Nick Pellow

fyi - I've asked the maven list about work arounds or fixes for this issue. The thread is here: http://www.nabble.com/getDependencyArtifacts-not-respecting-%3Cexclusions%3E-p20063925.html .

Hi David, Franz.

I would like to get started on this issue - however need some more information to try and reproduce the problem you are seeing.

Could you please provide your pom.xml, or the relevant snippets of your pom.xml . Specifically, I would like to see

• the dependency you have defined which has <exclusions/>
• your maven-surefire-plugin definition, if any
• your maven-compiler-plugin definition, if any.

As I understand this problem:

• your project has a dependency on artifact-A
• you have excluded one of artifact-A's dependencies (as you require a different version than is defined by artifact-A?)
• clover adds getProject().getDependencyArtifacts() (which does NOT respect artifact exclusions) to the compile time classpath
• your build fails, due to a version clash of the dependency you excluded.

Are these assumptions correct?

Cheers,
Nick

Hi,

I see that this has Priority: Minor.
Can we change it to blocker please? I already have a commercial Clover licence but I can't use it because Clover fails on my build now. I can't seem to be able to use it at all because of this bug.

Thanks,
David