Hello,
I think nobody jumped in the discussion because, to my knowledge, there is nothing new on this topic, the two existing solutions are still:
- Split the command in two to support this coverage merge. See the posts from here.
- Add a new module to the project, as advised by JaCoCo.
From a SonarSource perspective, you have to understand that we are not the maintainers of JaCoCo, we are only the messenger, importing what is provided to us. That being said, it’s true that the behavior you are looking for was possible thanks to a combination of JaCoCo and SonarSource tools. However, this was only possible thanks to .exec file, relying on it was not a good design since this is an internal representation, that external tools should not rely on. This was therefore never an explicitly intended feature.
We investigated the problem, and jump into the discussion to express our situation, and better understand the problem. This does not mean that we are requesting it or convinced by the feature though, we doubt merging coverage between modules is a good practice. I’m not sure making pressure on our side for a feature we are not convinced of would make sense.
At this point, we are well aware of your request, we will track it internally and make sure to take it into consideration regardless of our own opinion, but the final word to support this feature or not belongs to JaCoCo, and I can already say that there is nothing planned on the SonarSource side in the short future.
I hoe this clarifies the situation.