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: 8 rules found
obsolete
    Impact
      Clean code attribute
        1. "@Deprecated" code marked for removal should never be used

           Code Smell
        2. "Class.forName()" should not load JDBC 4.0+ drivers

           Code Smell
        3. "@Deprecated" code should not be used

           Code Smell
        4. "Collections.EMPTY_LIST", "EMPTY_MAP", and "EMPTY_SET" should not be used

           Code Smell
        5. Future keywords should not be used as names

           Code Smell
        6. "Enumeration" should not be implemented

           Code Smell
        7. Deprecated code should be removed

           Code Smell
        8. Deprecated elements should have both the annotation and the Javadoc tag

           Code Smell

        "@Deprecated" code should not be used

        consistency - conventional
        maintainability
        Code Smell
        • cwe
        • obsolete
        • cert

        Why is this an issue?

        More Info

        Code is sometimes annotated as deprecated by developers maintaining libraries or APIs to indicate that the method, class, or other programming element is no longer recommended for use. This is typically due to the introduction of a newer or more effective alternative. For example, when a better solution has been identified, or when the existing code presents potential errors or security risks.

        Deprecation is a good practice because it helps to phase out obsolete code in a controlled manner, without breaking existing software that may still depend on it. It is a way to warn other developers not to use the deprecated element in new code, and to replace it in existing code when possible.

        Deprecated classes, interfaces, and their members should not be used, inherited or extended because they will eventually be removed. The deprecation period allows you to make a smooth transition away from the aging, soon-to-be-retired technology.

        Check the documentation or the deprecation message to understand why the code was deprecated and what the recommended alternative is.

        /**
         * @deprecated  As of release 1.3, replaced by {@link #Foo}
         */
        @Deprecated
        public class Fum { ... }
        
        public class Foo {
          /**
           * @deprecated  As of release 1.7, replaced by {@link #newMethod()}
           */
          @Deprecated
          public void oldMethod() { ... }
        
          public void newMethod() { ... }
        }
        
        public class Bar extends Foo {
          public void oldMethod() { ... } // Noncompliant; don't override a deprecated method
        }
        
        public class Baz extends Fum {  // Noncompliant; Fum is deprecated
          public void myMethod() {
            Foo foo = new Foo();
            foo.oldMethod();  // Noncompliant; oldMethod method is deprecated
          }
        }
        
          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 Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use