maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham (JIRA)" <>
Subject [jira] Created: (MCLOVER-51) Clover causes build failure
Date Mon, 28 Aug 2006 18:27:48 GMT
Clover causes build failure

                 Key: MCLOVER-51
             Project: Maven 2.x Clover Plugin
          Issue Type: Bug
    Affects Versions: 2.1
            Reporter: Mike Perham
            Priority: Critical
             Fix For: 2.3

This is an interesting one.  Take module A and B where B depends on A.

I run clover to get the coverage numbers for A.  This installs A-clover.jar in the repo.
I modify some interfaces in A and install A.jar.  The tests pass.
I modify B to work with the new A interfaces and install B.  The compile and tests pass.
I run clover to get coverage numbers for B.

B fails to build because it says the code is not using A's old interfaces.  This is because
Clover tries to use A-clover.jar instead of A.jar in the classpath and the A-clover.jar was
built before the code in A was refactored.

I would suggest that you prefer the newer of { a.jar, a-clover.jar} in order to guarantee
that these types of build failures will not occur.  Marked as Critical because the plugin
is erroneously failing the build.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message