Hi Carlos,
JaCoCo does not use any cache.
Maybe you observe a compiler artifact here: For certain language
constructs (e.g. switch on enums) the Java compiler creates a static
initializer. Can you provide the source of the method where the coverage
browser jumps to?
Best regards,
-marc
On 07.08.14 00:19, Carlos wrote:
First, the tool stack: Java 7, Gradle 1.11, Jacoco plugin with
toolversion=0.7+, Spock 0.7+ with JUnit 4.8+
This particular class used to have a static initializer, as in "static
{..}", but was removed some time ago. As a matter of fact, it was
probably removed BEFORE I added the Jacoco plugin to the Gradle build.
Nevertheless, I've just now noticed that for whatever reason, Jacoco
seems to be working with the version of this class that may have this
static block still. It reports the coverage and branches-missed
percentage, but when clicked on, the coverage browser takes you to
inside a method in that class, not having anything to do with this
long gone static block.
Is there special cache location that could be the source of my
troubles here or something bigger I'm missing?
--
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]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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.
