EclEmma is based on JaCoCo agent, which transforms bytecode of classes for
recording of coverage.
By default JaCoCo agent doesn't transform classes that loaded by bootstrap
classloader ("java.lang.*" and some others) - this is controlled by agent
option "inclbootstrapclasses" ( see
http://www.jacoco.org/jacoco/trunk/doc/agent.html ) , which is however not
exposed in EclEmma preferences.
Also note that even when this option is set to "true", classes won't be
transformed if JVM loads them prior to start of agent.
In particular "java.lang.String" is loaded at the very beginning of JVM
startup.
Among other interesting JVM debugging options, there is "-verbose:class"
that can be used to see which classes are loaded and in which order.
Regards,
Evgeny
On Friday, January 26, 2018 at 10:00:24 AM UTC+1, [email protected] wrote:
>
> Cannot drill down into the methods of java.lang.String
>
> I wanted to demonstrate the effectiveness of EclEmma to a Japanese
> audience by generating a coverage report on JUnit Test Class based on
> java.lang.String for example, but I cannot drill down into the methods of
> java.lang.String. I have tried a few different java classes with no
> possibity of expand down into the methods.
>
> I experimneted using a different library (Apache Commons Codec
> org.apache.commons.codec.binary.Base64) and that works fine, I can expand
> down into all the methods..
>
> Can eclEmma produce reports on the base Java language (native java
> libraries eg java.lnag.* etc)?
>
> Will greatly appreciate your expertise, time and help on this.
>
> Jeff
>
>
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/138b13a9-47fb-4a59-9d38-eb90d22152f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.