On Wed, May 22, 2013 at 12:58 PM, Emmanuel Bourg <ebo...@apache.org> wrote:
> Le 22/05/2013 18:52, Gary Gregory a écrit : > > > The problem is that Jacoco produces bogus results as I recently emailed > > about the [io] component. The large portion of the code is reported with > 0% > > coverage which is completely wrong. This is apparently a known issue due > to > > the Jacoco use of 'probes' to analyze code which is not compatible with > the > > use of exceptions. > > What do you mean by probe? It doesn't instrument the code? > >From http://www.eclemma.org/faq.html#trouble02: "Code with exceptions shows no coverage. Why? The underlying JaCoCo code coverage library works with so called probes. Probes are inserted into the control flow at certain positions. Code is considered as executed when a subsequent probe has been executed. In case of exceptions such a sequence of instructions is aborted somewhere in the middle and not marked as executed." Gary > > > Emmanuel Bourg > > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
