Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarLint
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarCloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube

Secrets
ABAP
Ansible
Apex
AzureResourceManager
C
C#
C++
CloudFormation
COBOL
CSS
Dart
Docker
Flex
Go
HTML
Java
JavaScript
JCL
Kotlin
Kubernetes
Objective C
PHP
PL/I
PL/SQL
Python
RPG
Ruby
Scala
Swift
Terraform
Text
TypeScript
T-SQL
VB.NET
VB6
XML

Java static code analysis

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

Filtered: 36 rules found

suspicious

Impact

Clean code attribute

Recursion should not be infinite
Bug
"ThreadGroup" should not be used
Code Smell
"clone" should not be overridden
Code Smell
Unnecessary bit operations should not be performed
Code Smell
Switch cases should end with an unconditional "break" statement
Code Smell
"switch" statements should not contain non-case labels
Code Smell
A conditionally executed single line should be denoted by indentation
Code Smell
Conditionals should start on new lines
Code Smell
"indexOf" checks should not be for positive numbers
Code Smell
Method overrides should not change contracts
Code Smell
Methods should not be empty
Code Smell
Exceptions should not be thrown in finally blocks
Code Smell
Map values should not be replaced unconditionally
Bug
Week Year ("YYYY") should not be used for date formatting
Bug
"equals" method overrides should accept "Object" parameters
Bug
Methods should not have identical implementations
Code Smell
Assertion arguments should be passed in the correct order
Code Smell
Two branches in a conditional structure should not have exactly the same implementation
Code Smell
"Object.wait" should not be called on objects that implement "java.util.concurrent.locks.Condition"
Code Smell
JUnit4 @Ignored and JUnit5 @Disabled annotations should be used to disable tests and should provide a rationale
Code Smell
Assignments should not be made from within sub-expressions
Code Smell
Local variables should not shadow class fields
Code Smell
Nested blocks of code should not be left empty
Code Smell
"Math.abs" and negation should not be used on numbers that could be "MIN_VALUE"
Bug
Subclasses that add fields to classes that override "equals" should also override "equals"
Code Smell
Exit methods should not be called
Code Smell
Equality operators should not be used in "for" loop termination conditions
Code Smell
Number patterns should be regular
Code Smell
Modulus results should not be checked for direct equality
Code Smell
Conditionally executed code should be reachable
Bug
Tests should be kept in a dedicated source directory
Code Smell
"this" should not be exposed from constructors
Code Smell
Boolean expressions should not be gratuitous
Code Smell
Java parser failure
Code Smell
Exception handlers should preserve the original exceptions
Code Smell
"==" and "!=" should not be used when "equals" is overridden
Code Smell

Unnecessary bit operations should not be performed

intentionality - logical

maintainability

Code Smell

BlockerSonarSource default severity
click to learn more

suspicious

Why is this an issue?

Certain bit operations are just silly and should not be performed because their results are predictable.

Specifically, using & -1 with any value will always result in the original value, as will anyValue ^ 0 and anyValue | 0.

Available In:

Catch issues on the fly,
in your IDE

Detect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

Analyze code in your
on-premise CI

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Sonar helps developers write Clean Code.
Privacy Policy | Cookie Policy

In-IDE

SaaS

Self-Hosted