I agree with you, technically speaking there is no problem because it’s just a matter of removing a constraint to accept all languages and not just Java as it is the case today for the property sonar.junit.reportPaths
Then the question is where do we put this feature? Shall we keep it in SonarJava, I don’t think so. I would prefer this to have this kind of feature coming out of the box with SonarQube, ie not linked to any analyzer.