jacoco / jacoco Public

Co-authored-by: Evgeny Mandrikov <mandrikov@gmail.com>
Co-authored-by: Lukas Rössler <lukas.roessler@mysugr.com>

Ant task `java` with parameter `fork="false"` calls
`java.lang.System.setSecurityManager`,
however tests should not call it,
because as part of work on JEP 411
in JDK 17 it was marked as deprecated
(see https://bugs.openjdk.java.net/browse/JDK-8264713)
and in JDK 18 throws UnsupportedOperationException
unless system property `java.security.manager` set to `allow`
(see https://bugs.openjdk.java.net/browse/JDK-8270380).

By inserting the probe array access code at the beginning of the method
we accidently moved the range of the debug symbols of the method
parameters after the probe array access code. Actually the method
parameters are still valid from the very beginning of the method.

This offset in the method parameter's debug symbols may confuse tools
like Jandex.

A sequence of instructions between two probes may correspond to several lines.

In that case, as identified in #1223, an exception may "hide" the executed status of several lines, and not just one.

Seems that Maven 3.8.2 contains bug, which prevents us from using it.

The module `org.jacoco.core.test` provides test tools for other tests
modules and is used as a dependency in several places.

…cies (#1205)

…#1194)

Records and Pattern Matching for instanceof are finalized in Java 16,
so no need to test them as preview features in earlier versions.

for-loop with range expression whose bounds are constants with end
less than start is folded into nop by Kotlin compiler version 1.5,
without constants in for-loops behaviour is the same for compiler
version 1.5 as for earlier versions.

Co-authored-by: troosan <antoine.de.troostembergh@gmail.com>
Co-authored-by: Marc R. Hoffmann <hoffmann@mountainminds.com>

…1176)

)