maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol (JIRA)" <>
Subject [jira] Commented: (MCLOVER-26) dependencies omitted from classpath during clover compile
Date Mon, 03 Apr 2006 16:37:44 GMT
    [ ] 

Vincent Massol commented on MCLOVER-26:


I've just tried with maven 2.0.2 and it worked fine. As you've done the checkout of the clover
plugin, you should have some tests in src/it/. You can try running them ("mvn site" for example).

Now your example is using Clover plugin v2.0 and the configuration has changed quite a lot
for version 2.1. Some remarks on your pom snippet:
- you shouldn't need to modify the outputDirectory. The default is ${project.reporting.outputDirectory}/clover
which results in the report being in site/clover.
- the licenseFile is now named licenseLocation but we support the old notation
- you need to call clover:instrument as clover:clover now only generates a report from an
existing database (see

All these changes should not lead to the exception you're seeing though.

I'd recommend you try with the samples I've mentioned and see how it goes.


> dependencies omitted from classpath during clover compile
> ---------------------------------------------------------
>          Key: MCLOVER-26
>          URL:
>      Project: Maven 2.x Clover Plugin
>         Type: Bug

>     Versions: 2.0
>  Environment: java 1.4.2_05, solaris os, anthill pro 2.5
>     Reporter: jake pezaro
>     Assignee: Vincent Massol
>      Fix For: 2.1
>  Attachments: anthill_RiskCacheServer-Deploy-Builder_log.txt, pom.xml, pom.xml, pom.xml
> my project builds & tests sucessfully using when using the normal lifecycle (compiler:compile),
however when clover runs the compile task (as part of mvn site) the compile fails.  i have
attached a debug log from such a build to this bug.  from this i can see that the classpath
used by the clover compile is missing a dependency (com.vcint:VcCommons:jar:2.2.1-SNAPSHOT).

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