Can we deploy custom Plugin for PL/SQL (with *.sql files) along with Out-of-the-box PL/SQL plugin in Enterprise Edition? We see server complaining on which plugin to use for .sql files in the log messages.
Is the “Adding XPath rules directly through the SonarQube Server web interface” is the only option for Custom SQL rules?
Is there a work around to let SonarQube server to let two different plugins run for the same language sequentially?
Hi,
No, you can’t. SonarQube permits the loading of multiple plugins for the same language only if the subsequent plugin contributes to the rules of an existing plugin that allows for this extensibility. It’s not the case for the SonarPLSQL plugin, it can’t be extended with custom plugins (unlike its alternative).
You need to adjust the *.file.suffixes properties to make only one of the plugins analyze the sql files.
Thank you so much Scott for your quick response.
Hey all!
I believe the distinction here is that only one plugin can declare a language. Meanwhile, if you have a plugin that generates issues but doesn’t try to contribute measures, code duplications, syntax highlighting… you are good to go. Of course, you won’t be able to rely on any APIs from the “official” PL/SQL plugin and will have to start from scratch parsing your code.
Our developers gave me an example to share: sonar-iac raising issues on Java code.
Thank you, Colin.
That’s helpful to know. I’m curious, though… Would a plugin that adds PL/SQL rules via this method, and perhaps includes something like simplified utPLSQL report import, be eligible for inclusion in the Marketplace under the guidelines outlined in Deploying to the Marketplace?
Hi @felipebz,
If you’re not declaring a ‘native’ SonarQube language. If you’re just enhancing what’s available for the language, then yes*.
HTH & looking forward to your PR 
,
Ann
* Assuming you meet the Marketplace requirements