You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Ate Douma (Commented) (JIRA)" <ji...@apache.org> on 2011/10/05 00:40:34 UTC

[jira] [Commented] (RAVE-245) Integrate Cobertura maven plugin

    [ https://issues.apache.org/jira/browse/RAVE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120545#comment-13120545 ] 

Ate Douma commented on RAVE-245:
--------------------------------

I've got a fix or workaround by adding an explicit xercesImpl:2.9.1 dependency on the maven-openjpa-plugin itself.
How the classloader conflict exactly is occurring I don't claim to know, but the cobertura plugin runs a forked test lifecycle build before, which I think might 'lose' the scope on the xercesImpl dependency.
By explicitly adding this as a openjpa plugin dependency I think this enforces it to be picked up, even through the forked lifecycle.
Anyways, this solved it for me, locally. I haven't looked into the Jenkins configuration but I guess you (Anythony) can pick it up from here again?
                
> Integrate Cobertura maven plugin
> --------------------------------
>
>                 Key: RAVE-245
>                 URL: https://issues.apache.org/jira/browse/RAVE-245
>             Project: Rave
>          Issue Type: Story
>          Components: build & development
>            Reporter: Anthony Carlucci
>            Assignee: Ate Douma
>            Priority: Minor
>
> Setup the Rave build to run the Cobertura maven plugin to generate unit test coverage numbers for local development as well as on the Apache Jenkins server.
> 1) Modify the rave-project pom.xml with the cobertura-maven-plugin
> 2) Modify the Jenkins ci build for Rave to execute the mvn cobertura:cobertura  goal
> 3) Modify the Jenkins project module for Rave to publish the coverage reports for rave-commons, rave-portal, and rave-shindig

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira