[ http://jira.codehaus.org/browse/MCLOVER-42?page=comments#action_68194 ]
Vincent Massol commented on MCLOVER-42: --------------------------------------- Hi Erwin, I'm not able to reproduce your problem. We do have one working test in the clover plugin functional test suite that uses tesResources so I thought this would be working. The clover plugin doesn't do anything with testResources. As part of its lifecycle it simply calls mvn:test which is why I don't understand the problem. What would help would be if you could provide a small project sample that reproduces your issue. Thanks -Vincent > 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
