Incorrect coverage report probably due to groovy optimisation

[rolnico]

Describe the current behavior

Coverage report shows 6 uncovered conditions:
In the TimeSeriesDslLoader constructors creating a new GroovyCodeSource object, the coverage is partial (1 of 7 conditions covered).

Describe the expected behavior

There are no conditions to cover there.

Describe the steps

Test coverage on PR #103

Environment

No response

Relevant Log Output

No response

Extra Information

Might be due to groovy compiler optimisations

[rolnico]

Interesting links : https://docs.groovy-lang.org/latest/html/api/org/codehaus/groovy/control/CompilerConfiguration.html#setOptimizationOptions(java.util.Map)
https://docs.gradle.org/current/dsl/org.gradle.api.tasks.compile.GroovyCompileOptions.html#org.gradle.api.tasks.compil[…]Options:optimizationOptions

[rolnico]

other interesting link: https://pbetkier.github.io/2014/08/07/groovy-code-coverage-issues.html

[olperr1]

In the CI, the Run SonarCloud analysis task of maven_ubuntu.yml is the one generating the jacoco reports. It uses already compiled java classes but it re-compiles the groovy code.
If maven options disabling groovy code optimization exist, they should be used at this step.