Within several posts I have read that the usage of the sonarsource maven parent pom is discouraged for community plugins.
If so, why is that? Is it just meant to be used for sonarsource developers - e.g. integration into company ci? Or do you think it to be over-engineered for most purposes?
From my point of view it’s got many sane defaults from which every plugin developer can benefit.
Finally, if discouraged, is the usage of the parent pom a show stopper? The sonar-pmd plugin still uses (an updated version of) the parent pom…