I should have also noted there (but you can see it in the issue and the GWT docs), that even once you patch you don't get the ease of choosing a coverage tool and the regular Maven way for reports, etc - you have to use Emma.
I have successfully used Emma for quite some time, with GWT and Maven via GWT-Maven, but it's not for the faint of heart (patch, patch, etc). GWT 1.6 should help with make this a lot easier, but it is my understanding it will still be Emma only. (Cobertura won't work - has to do with what code actually gets run during GWTTestCase tests, and the way the classpath is constructed - even instrumenting classloaders don't have real access, like I said, long story.) On Jan 29, 7:00 pm, Matt Raible <[email protected]> wrote: > I've added the cobertura-maven-plugin[1] to my project and can > successfully generate code coverage reports for my JUnit tests. > > However, it doesn't pick up classes that extend from GWTTestCase. Is > it possible to use the cobertura-maven-plugin for these classes and > the gwt-maven plugin? > > Thanks, > > Matt > > [1]http://mojo.codehaus.org/cobertura-maven-plugin/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
