PLUGINAPI-34 add aliases for sonar.test.inclusions and sonar.test.exc…

[benjamin-campomenosi-sonarsource]

No description provided.

[sonarsource-next]

SonarQube Quality Gate

Maintainability Rating on New Code (is worse than A)

See analysis details on SonarQube

Fix issues before they fail your Quality Gate with SonarLint in your IDE.

[damien-urruty-sonarsource]

I'm thinking about really edge cases, what if users define both the legacy and alias properties with different values ? Will you use the legacy property in priority ? Do you plan to display a warning too, or an error ? I am not sure it should be documented in JavaDoc, as it's such an edge case. Up to you

I think the fact that it's an alias could be documented in the JavaDoc, to lower confusion for people seeing both and wondering what the difference is.

[benjamin-campomenosi-sonarsource]

In Sonarqube, if we define both properties, we merge the value of both.. But a warning is log each time we use the alias..

If we look at the Why/What of SONAR-16491, I don't think we have to document the aliases, they are there to avoid the users to be too confused . Maybe we can discuss this edge case with the PM and the doc team?