Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • This service only shows "Added Violations", not fixed ones. Therefore the number you see in this service can be different from the dashboard.
  • The algorithm used to detect if a violation is new is very good but still perfectible. Therefore new violations can sometimes appear only because Sonar did not recognize it existed already
  • You are looking at a period of X days which goes beyond the first analysis made after migration to Sonar 2.5. In this case there can be a discrepancy due to the fact that prior to 2.5, Sonar was not collecting the info necessary to build this service. This issue will disappear as soon as period does not go beyond first analysis.
Failed to analyse a project as another analysis on the same project seems to be running at the same time (Sonar 3.4 only)

In Sonar 3.4 (SONAR-3306) a new semaphore mechanism has been introduced to prevent launching several analysis on the same project in parallel. But in some cases when an analysis of a project is unexpectedly interrupted, the lock of the semaphore is sometimes not released and in such case it's up to the Sonar administrator to relaunch the project analysis with the property 'sonar.forceAnalysis=true'. This limitation has been fixed in Sonar 3.5 (SONAR-4053). 

How to remove false-positive violations?