We’ve mentioned this in a few places but not made a big deal of it yet: we’re working on a Ruby analyzer ourselves, and it’s only a few weeks from release.
Unfortunately, that puts your plugin in conflict with the competition clause of the requirements because you no doubt
declare the language
“claim” the file extension
Which means the user would experience errors (not just warnings) with our to-be-shipped-by-default analyzer and yours together. We’re also planning to import Rubocop issues and SimpleCov reports.
So I can’t add your plugin to the Marketplace at this time. However, if your plugin provides additional features (I haven’t looked closely) and you would like to make it available as an additional Ruby analyzer (you’ll have to wait until after SonarRuby comes out) then I’d be happy to reconsider it later.
In the meantime, I can only say I’m sorry for your wasted effort.
No worries. I had worked on this only because of the absence of a Ruby analyzer. I’m glad you all are working on one. I can maintain this plugin until yours is released and them deprecate it.
Over the next few weeks you’ll see Ruby support coming in SonarLint , and in SonarQube too ! We’re aiming for SonarQube availability with SonarQube 7.4 (early October).
SonarQube 7.4 is around the corner, should be out within the next couple of weeks. Watch out SonarQube website/twitter/announcements and you’ll get the news soon as it happens.
: