On 24/01/2020 08:16, Robert Varga wrote:
> On 14/01/2020 23:09, Anil Belur wrote:
>> Greetings Robert:
>
> Hey Anil,
>
> sorry for the late reply.
>
>> Trying to catch up on where we are with the sonarcloud migrations. I
>> think another issue has been identified with 0% coverage, that is caused
>> by an update on the Java analyzer.
>
> Ah, good thing we did not do a straight-up migration then :)
>  
>> With sonarcloud it's no longer possible to import jacoco.exec reports,
>> and the workaround suggested is to use XML format. This needs to be
>> fixed in the pom files.
>
> Okay, so if I am getting this correctly, this is covered in
> https://community.sonarsource.com/t/jacoco-coverage-reporting-differently-in-sonarcloud/8256
>
>> Example on how this is fixed on an external project:
>> https://github.com/synyx/urlaubsverwaltung/pull/930/files
>
> Right, and an example is here:
> https://github.com/SonarSource/sonar-scanning-examples/tree/master/sonarqube-scanner-maven/maven-multimodule,
> unfortunately it does cover the way we are doing things (i.e. top-level
> merged report *without* enumerating all artifacts as dependencies).
>
> I will need to look into this further.

Okay, I do have a prototype here:
https://git.opendaylight.org/gerrit/c/odlparent/+/88440

Can somebody test it, please?