Hi Greg, the changes look good to me. Do you mind adding instructions on how to run the test coverage to our wiki's developer section? It may also make sense for us to run them on the integration server and put the results online in an automated way.
Tobias On 08.06.2012, at 00:58, Greg Logan <[email protected]> wrote: > Is anyone using Clover to look at unit test coverage aside from me? I > tried getting it working as is, but I couldn't seem to get the maven > plugin to work without modifying the main pom. Since I'm not terribly > familiar with the pom, and I'm not sure what my changes might affect, I > figured the list should hear about it first. The attached patch > contains my changes for 1.4.x, and should apply for 1.3.x as well since > the changes are identical. Basically I moved the plugin definition up > in the pom file (to correspond with Atlassian's current instructions) > and updated the version. Are there any objections to me committing this > change into the main repo? > > G > > P.S. For those interested in generating the Clover output, apply the > patch, then from the top of the branch run mvn clover2:setup test > clover2:aggregate clover2:clover -Dcheckstyle.skip=true -P > admin,dist,engage,worker,workspace,serviceregistry,directory-db,capture,oaipmh,export,gstreamer-launch-service. > The skipping of checkstyles is especially important since otherwise > checkstyles objects to the instrumented source files. > <pom.diff>_______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
