For what it is worth, Maven 2.2.1 with the stock Emma plugin (version 1.0-alpha-3) works just fine with gwt-maven-plugin:test. There are certainly issues with Maven 3, but as we run test coverage outside of our normal nightly builds, we drop to Maven 2 for coverage details.
With the gwt:test goal bound to the test phase, we just run `mvn emma:emma` and get a nice html report (as well as the .ec and .em files). I've been using this strategy since at least GWT 2.2, and it works up to and including GWT 2.5.0-rc1. -Colin On Wednesday, September 26, 2012 8:14:51 AM UTC-5, Joseph Lust wrote: > > Chris, > > Indeed, it is old. It still works however, and GWT Coverage is more > important to me than moving to v2.1. When getting my whole team to use it, > this is easier than asking folks to explode/repackage the jars as the > official GWT fix requires. I've looked at the patch on the Google site, but > the code it patches/namespaces are now totally different. On asking the > Emma team to merge the old fix, hoping they'd have the expertise, they > responded with "wont-fix". So, if anyone is bored, and familiar with > Jacoco, I'll trade you a beer for a patch. :) > > > Sincerely, > Joseph > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/F8ZFCrpiSTIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
