[ http://jira.codehaus.org/browse/MCLOVER-51?page=comments#action_73558 ]
Vincent Massol commented on MCLOVER-51:
---------------------------------------
Hi Mike,
Yes, an interesting use case... I agree that taking the newer of {a.jar,
a-clover.jar} is probably the best way around this.
Thanks
> Clover causes build failure
> ---------------------------
>
> Key: MCLOVER-51
> URL: http://jira.codehaus.org/browse/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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
