maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jake pezaro (JIRA)" <>
Subject [jira] Commented: (MCLOVER-26) dependencies omitted from classpath during clover compile
Date Thu, 30 Mar 2006 14:16:44 GMT
    [ ] 

jake pezaro commented on MCLOVER-26:

hi vincent

that could be difficult.  this error only occurs on one project out of the 20+ projects that
we have.  i don't know what causes this project in particular to fail, and i am not able to
send you the entire project.  however i have done a bit more examination and found the following:

comparing the classpaths (in the attached logfile) at line 510 and at line 1883, the classpath
has 12 items in both places, however in the line 1883 (where the build fails) one one of the
dependencies has been replaced by a clover dependency as follows:

missing dependency: /export/integration/m2/repository/com/vcint/VcCommons/2.2.1-SNAPSHOT/VcCommons-2.2.1-SNAPSHOT.jar
replaced by: /export/integration/m2/repository/clover/clover/1.3.11/clover-1.3.11.jar

if you could give me some pointers as to where this classpath is being generated or altered
i will try and locate the problem here.



> 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
>  Attachments: anthill_RiskCacheServer-Deploy-Builder_log.txt
> 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