Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-6553

Drop the Design related services and metrics


    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2
    • Component/s: None
    • Labels:


      Facts are the following:

      • Few people are using and giving feedback on the Design features (some bugs were discovered very long after they were introduced)
      • This is not surprising because those features currently do not contribute issues nor technical debt, so developers can't manage those "flaws" (for instance, it's impossible to tell that this cycle between package is normal whereas this one is a real problem)
      • What's more, those features are mainly provided on Java projects, so SQ does not offer a consistent experience across different projects
      • Even in the Java world, not all projects benefit from those services because some (like Libraries or Dependencies) are heavily coupled with Maven
      • Features like Libraries or Dependencies do not directly relate to source code analysis, so there's no real reason why we should keep them
      • Features like the DSM can be useful (only for Java projects...), but in its current format it's unusable and most users don't understand how it can be used

      Based on all those facts, all design features should be dropped:

      • Dependencies service
      • Libraries service
      • DSM service
      • Design widgets and metrics

      This will give the opportunity to start from scratch on this topic and offer features that fully match the philosophy and the targets of the SQ platform. This is what is called "Cartography" on the SQ Roadmap page.


          Issue Links



              • Assignee:
                julien.lancelot Julien Lancelot
                fabemn OLD - Fabrice Bellingard
              • Votes:
                0 Vote for this issue
                18 Start watching this issue


                • Due: