What is a reasonable order of Java modifiers (abstract, final, public, static, etc.)?

java

best-practices

coding-standards

java-modifiers

byAnton Shumikhin·Mar 11, 2025

According to the Java Language Specification (JLS), the recommended modifier sequence for clarity is as follows:

public abstract class Example {
    public static final int RELIABLE_CONSTANT = 1; 
    //Did you notice 'constant' being 'final'? Good one, right?
}

Key insights:

Initiate with access modifiers (public, protected, private)
Follow with abstract (for classes/methods), static (for contexts)
final is ideal for constants/immutable classes This order allows for better readability and consistency within your Java codebase.

Understanding the Modifier Placement Protocol

The JLS and Java Style Guidelines rolled out by OpenJDK recommend a standard order of modifiers. The sequence - public, protected, private, abstract, static, final, transient, volatile is not just a matter of style.

1. Order according to scope and behavior

The principle entails starting with the broadest scope and narrowing down to specific characteristics:

Access modifiers: Who can use the method or variable? (public, protected, private)
Non-access modifiers: What is the behavior of the method or variable? (abstract, static, final, transient, volatile)

2. Deal with odd modifier out

Modifiers such as strictfp rarely make an appearance in everyday Java code. For the sake of code simplicity and readability, exclude such modifiers unless necessary.

3. Team collaboration and coding norms

By adhering to a common modifier arrangement, your team can maintain coding standards and smooth peer review process, letting the primary focus be on logic rather than syntax.

Coding for the future

Adhering to a standardized guideline keeps your code ready for future changes. As Java keeps evolving, meticulously ordered modifiers will facilitate smooth transition towards new language features.

Adding order to avoid chaos

In the broader perspective, an arranged sequence of modifiers can influence certain tool's performance. For example, the reflection API might inspect Java classes more efficiently if modifiers are placed predictably.

Authoritative practices: Your go-to guide

With the ever-growing Java ecosystem, look out for JLS and JVM specifications for trusted advice. They encapsulate insights from the wider community and are the gold standard in the field of Java development.

explain-codes / Java / What is a reasonable order of Java modifiers (abstract, final, public, static, etc.)?

Linked

Should methods in a Java interface be declared with or without a public access modifier?



Difference between final static and static final



Does Java have a "private protected" access modifier?



Is there a way to simulate the C++ 'friend' concept in Java?



Hiding certain methods from other packages

