SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 17 rules found
design
    Impact
      Clean code attribute
        1. Circular dependencies between classes across packages should be resolved

           Code Smell
        2. Circular dependencies between classes in the same package should be resolved

           Code Smell
        3. The Singleton design pattern should be used with care

           Code Smell
        4. Methods should not perform too many tasks (aka Brain method)

           Code Smell
        5. Classes should not depend on an excessive number of classes (aka Monster Class)

           Code Smell
        6. Constructors of an "abstract" class should not be declared "public"

           Code Smell
        7. Tests should use fixed data instead of randomized data

           Code Smell
        8. Tests should be stable

           Code Smell
        9. Spring components should use constructor injection

           Code Smell
        10. Constructor injection should be used instead of field injection

           Bug
        11. "ThreadGroup" should not be used

           Code Smell
        12. Classes without "public" constructors should be "final"

           Code Smell
        13. Public methods should not contain selector arguments

           Code Smell
        14. Double-checked locking should not be used

           Bug
        15. Two branches in a conditional structure should not have exactly the same implementation

           Code Smell
        16. String literals should not be duplicated

           Code Smell
        17. Utility classes should not have public constructors

           Code Smell

        Circular dependencies between classes across packages should be resolved

        adaptability - modular
        maintainability
        Code Smell
        • architecture
        • design

        This rule reports circular dependencies between classes across different packages.

        Why is this an issue?

        How can I fix it?

        More Info

        Circular dependencies occur when two classes reference each other, either directly or indirectly. This means that the classes' dependency structure does not represent an intuitive hierarchy, which makes it harder to understand and maintain.

        Compared to S7027, this issue is even more significant when a cycle crosses package boundaries because:

        1. It disrupts the dependency hierarchy or layer structure even between packages.
        2. It spreads the problem across more distant locations in the source code.

        What is the potential impact?

        Circular dependencies increase the architectural complexity of the code, reducing its readability, extensibility, and maintainability. As the project grows, circular dependencies often lead to more circular dependencies, further complication of the architecture and increasing technical debt. Over time, untangling these dependencies becomes increasingly difficult.

          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.8

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use