sayit | SayIt - a component | Runtime Evironment library

The problem seems to start at Line # 9

JaCoCo analyzes .class files, not source files. The Scala compiler may produce multiple .class files from a single source file. Your SayHello.scala class most likely contains a companion object. An object is always compiled to a class of the same name with $ at the end, which implements the companion object singleton at the bytecode level. If you go to your target/classes directory, you'll most likely see those two files there - SayHello.class and SayHello$.class.

Two records in the JaCoCo report correspond to those two class files. The dot at the end instead of a $ is most likely a jacoco report rendering issue.

To skip the companion object class from analyzing, just add it to your exclusion list:

Solution was to set sample time to 30 sec in block parameters(subsystem).

Braced-init-list has no type and cause template argument deduction fails.

Non-deduced contexts

In the following cases, the types, templates, and non-type values that are used to compose P do not participate in template argument deduction, but instead use the template arguments that were either deduced elsewhere or explicitly specified. If a template parameter is used only in non-deduced contexts and is not explicitly specified, template argument deduction fails.

1. The parameter P, whose A is a braced-init-list, but P is not std::initializer_list, a reference to one (possibly cv-qualified), or a reference to an array:

You can specify the template argument as std::initializer_list explicitly to bypass the deduction,

So, after 3 days I finally got an answer to my question. And it says that I am stupid :) because in the article at the very end the author provided the example with correct behavior and it works in my case. However, it doesn`t work in my other test with slf4j and logback dependencies. But to my surprise, the code without system class loader works. In the nutshell, I try to use different versions of slf4j and logback.

Pom.xml: