property 'sonar.cxx.coverage.reportPath' should be made using 'getStringArray' method. The SonarQube plugin using this property should be updated

[guwirth]

20:56:30 [sonar:sonar] Access to the multi-values/property set property 'sonar.cxx.coverage.reportPath' should be made using 'getStringArray' method. The SonarQube plugin using this property should be updated.

To be updated (see also #1381)

[guwirth]

https://groups.google.com/forum/#!topic/sonarqube/3JCtRo8r_Yc

With the move from Settings to Configuration, I'm trying to enforce some consistency between property definition, and property "use".

On server side and scanner side, there are some special treatments for multi-valued properties (in particular to support comma inside a value). This will work best when:

• multi-valued property is declared as multi-value in the property definition
• values are read using provided getStringArray() (and not get() + split yourself)

So when moving to use org.sonar.scanner.config.Configuration, a warning will be emitted when:

• you read with get() a property declared as multi-valued
• you read with getStringArray() a property not declared as multi-valued

For completeness @ Günter: SONAR-9478 , with related note in API changes documentation :

• org.sonar.api.config.Configuration as a clean replacement of org.sonar.api.config.Settings. A warning will be logged when multi-valued properties are not properly declared/read using Configuration#getStringArray.