What's the difference between requires and requires static in module declaration

Question

What's the difference between requires and requires static module statements in module declaration?

For example:

module bar {
    requires java.compiler;
    requires static java.base;
}

Weary

Possible duplicate of Does the Java 9 Module system support optional dependencies? – Chaconne

@Chaconne Though I support the duplicate vote. But not very sure if the linked post state the difference between the two. Anyway, I also do believe that the primary motive behind this question could be to know about static modifier on the requires directive itself. – Gelasias

I don't consider this to be a duplicate. While both questions deal with the same topic, they have very different angles. This question here will be found by people searching for the syntax, the other one by people having the requirement to make a dependency optional. – Circumbendibus

Answer 1

A requires clause expresses that the required module is needed at compile and run time. Consequently, when the module system encounters such a clause during module resolution (the phase in which module descriptors are processed and dependencies are resolved) it searches the universe of observable modules (the modules in the JDK and on the module path) and throws an error if it doesn't find the module.

A requires static clause expresses a dependency that is optional at run time. That means at compile time the module system behaves exactly as described above.

At run time, on the other hand, it mostly ignores requires static clauses. If it encounters one, it does not resolve it. That means, if an observable module is only referenced with requires static, it does not make it into the module graph! This can be a little surprising at first. If, on the other hand, the module makes it into the graph in some other way (required by some other module, added manually with --add-modules, drawn in by service binding), all modules that have an optional dependency on it can read it.

Circumbendibus

Could you provide use case when I need requires static ? Why should I want to have some dependency only during compile time? – Nehru

I think that goes beyond the scope of this question, but I give two examples in my blog post about optional dependencies. – Circumbendibus

Answer 2

The primary difference between the two is that in case of

requires static foo.module;

The dependence is mandatory in the static phase, during compilation, but is optional in the dynamic phase, during execution while on the other hand

requires bar.module;

Is added to declare that the module depends, by name, upon some other modules, at both compile time and run time.

Gelasias

Could you provide use case when I need requires static ? Why should I want to have some dependency only during compile time? – Nehru

@Nehru lombok and other annotation processing tools (e.g. non-runtime annotations) – Caoutchouc

@Caoutchouc post this as an answer, it took me 5 minutes to read both answers, to only "get it" via your comment. And this happened the third time in 3 years now! please... – Dispute