Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Fixing some SonarQube-issues #588
Not sure if you're aware, but the people behind SonarQube (tool for code analysis) has a public instance where they scan various free and open source projects regularly, FitNesse included. (See http://nemo.sonarqube.org/dashboard/index/390646 for more details)
This branch is work in progress, but I thought I'd at least let you know the list of issues exists. I've started with some of the low-hanging fruits and plan to work on reducing the amount of open issues. :)
referenced this pull request
Jan 25, 2015
Hard to say about the config file. I only found the page from their website and don't know much about the setup/how they run the scans. Thus my question, I wasn't sure whether FitNesse had signed up somehow or if they have simply found a bunch of projects and scan them. Useful either way, though.
I would guess they are probably running the scans using the SonarQube Runner (http://docs.sonarqube.org/display/SONAR/Analyzing+with+SonarQube+Runner). It is possible to run it as an ANT task as well, though that seems to require defining it in build.xml. So I find it a bit unlikely that they would keep a patch for that around and re-apply it on top of latest HEAD every once in a while just to run scans.
I'll look into it and see if I can find anything (and continue fixing issues :)). Did you have any particular configurations in mind? I've been playing a bit around with SonarQube locally so I would anyways be able to test it out if I can get it working there.