sonar-xquery-plugin
sonar-xquery-plugin copied to clipboard
malteseduck
SonarQube 6.x Support
Do you have plans to support SonarQube 6.x? Or do you have a work-a-round how to run the existing plugin on 6.2?
I had kind of dropped off working on this a long time ago because it didn't seem useful to most, but maybe it is time to fix it. Where I was using it before stopped believing in doing static code analysis because it is "too much of a pain" so I lost interest. I will have to look at how much of a pain it would be to update to the newer APIs
Ok, have also experienced a lot of headwind for this stuff.
If SCA (Static Code Analysis) is only about Code-Style-Checking then it could make more noise then solving issues. But if you have a set of reliable Rules to find Anti-Patterns with Performance, Security or Maintainance impact this could be helpfull. In one of my projects they have a long checklist with company and project compliance stuff. Boring stuff if you have to check this all manually. For this reason I think about to setup a sonarqube beside our existing Jenkins.
Another really nice thing is the sonarlint solution, which could work together with sonarqube profiles so every develeoper can check his own code before checkin.
Perhaps I could investigate a bit and build a guide (if there is not allready one) how to add / remove or customise existing rules for this xquery plugin?
Hey there. Just as a heads up - our IT forced an update of Sonar on us, so we are trying to figure out how to update this plugin as well. Happy to test/collaborate/develop. (In the process of installing Sonar v6 locally to get an idea what we are missing)
Hey malteseduck , We are also interested in using Sonar v6 with this plugin.
Hi Malteseduck, From our company we are doing a lot of Xquery coding. We are currently using SonarQube 6.7 and I am interested if you have any plans to upgrade this plugin for a newer/latest version of SonarQube. Thank you in advance.
Plans without time. I started looking into it, but there have been a lot of changes in the API and there would be a lot of rewriting, so it still sits there, sad and un-updated.