So I figured it out, all I had to do was add the JaCoCo agent to Liberty's JVM arguments and exec files were produced exactly how I wanted them to be. Running the raw files through the simple ExecDump.java API example from the EclEmma site showed probes/coverage exactly how I'd expect. Of course creating a report from the exec file showed 0% coverage.
I threw everything I could at this thing. The only method that worked was actually opening the war files, extracting the jar files that I had instrumented from them, extracting the class files from the jars, and loading them into my HTML reporter. And even then the generated report did not drill down to source code level, only method level. Unless there's a silver bullet I don't know about then it seems as though I've hit a dead end. At this point I don't think this is an issue with JaCoCo so much as it is with how war files are packaged and executed within their container. Is this the glass ceiling for JaCoCo coverage? If anybody has been able to automate runtime instrumentation of web services and filter all 3rd party libraries from coverage with the Maven plugin (or some minimally dependency-invasive method) then I'd love to hear about it. If not, then I do realize it's not a fault of JaCoCo. Offline instrumentation is just a kind of necessary evil. Until then, I'll remain grateful for the help you've given me in the past, Marc... I really do appreciate that you have a presence in the community. Cheers! -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
