[ http://jira.codehaus.org/browse/MCLOVER-42?page=all ]
ErwinTukker closed MCLOVER-42:
------------------------------
Resolution: Fixed
Vincent,
I did some more digging and found out that the problem was not the testResource
but that a test-jar not being on the classpath was the actual problem. I know
that an issue was already raised for this. So closing this one.
Any idea when 2.2 will be released, since the test-jar is really 'bugging' me.
Brgrds, Erwin.
> clover:instrument does not take testResources into account
> ----------------------------------------------------------
>
> Key: MCLOVER-42
> URL: http://jira.codehaus.org/browse/MCLOVER-42
> Project: Maven 2.x Clover Plugin
> Type: Bug
> Versions: 2.1
> Reporter: ErwinTukker
> Assignee: Vincent Massol
> Fix For: 2.2
>
>
> My pom.xml includes some testRecources, see an example below.
> {code:xml}
> ...
> <build>
> <testResources>
> <testResource>
> <directory>../SubProjectA/src/test/resources</directory>
> </testResource>
> </testResources>
> </build>
> ...
> {code}
> Note that the testResource is an 'external' resource, in this case it is in
> another sub project. The reason for this is that the testResource is shared
> by multiple projects and it just happens to be located in SubProjectA.
> Now, when I run mvn:test, all tests run ok. However when running mvn
> clover:instrument or mvn:site, tests fail because the testResource is not on
> the classpath.
> Brgrds, Erwin.
--
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
