Your chances of getting coverage information are next to zero. Just leave your GWT projects out of the code coverage mix, for now. The GWT team is making this easier in GWT 1.6, but even then they use Emma, and I am not sure if it will work with Clover. (I would like to see it work with any coverage tool, and they may be working on that too, not sure.)
The GWTCompiler isn't a regular compiler, of course, and GWTTestCases are compiled and run by IT, not by regular javac. Even instrumenting classloaders can't get to the JDT stuff the 1.5 and under compiler is using. Here is a little more about the Emma support: http://code.google.com/p/google-web-toolkit/wiki/EmmaSupport. I have used Emma with 1.5, with the patch, and my patch for the patch, but it's a long story: http://code.google.com/p/google-web-toolkit/issues/detail?id=779 (note that that says FixedNotReleased, maybe 1.6M1 would help, but it still seems Emma focused to me) On Feb 19, 12:44 pm, "Brian H. Mayo" <brian.h.m...@gmail.com> wrote: > We are trying to setup our Continuous Integration environment and have > hit a bit of a snag. > > We are running Atlassian's Bamboo CI server. We have a parent project > with child modules. We have a Web module with GWT. We use Maven2 for > our build and dependency management. We are using Clover2 to handle > our code coverage reporting. > > In the lifecycle of Clover, at one point it instruments all code and > calls compile. When it does this, the GWT Maven plugin attempts to > compile the code into the Javascript. Since the code is fully > instrumented, I get an error that it wants the source code for the > Clover classes. > > I am not sure what to do here, I image I can just simply put excludes > in for all of the GWT client code that would participate in a Java to > Javascript compile, but I do not want to do that (not even sure if > that will work the way I am thinking). > > Anybody out there with the same issue that has a work-around? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to gwt-maven@googlegroups.com To unsubscribe from this group, send email to gwt-maven+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
