https://dev.java/learn/packages/ is out of date, doesn't mention `import module` added in JEP 511 in Java 25

[willy-b]

Hello dev.java team!

In case it is useful, I am reporting where in this tutorial it may be most helpful to add just a couple of sentences to stay up to date with the new import module feature (JEP 511) that came out in Java 25 ( https://openjdk.org/jeps/511 ).

---

In the latest version of https://dev.java/learn/packages/ (archived as is at https://web.archive.org/web/20260527153107/https://dev.java/learn/packages/ ),

The choices provided for using public types from other packages are out of date for module imports:

To use a public type that is in a different package, you have three choices:

1. use the fully qualified name of the type,
2. import the type, or
3. import the entire package of which the type is a member.

Now, since JEP 511 in Java 25 ( https://openjdk.org/jeps/511 ),

there is a 4th choice:

[suggested] 4. import the entire module (all exported packages) which exports the package of which the type is a member.

as one can do module level imports, like import module java.base , which as an example,

then has "the same effect as 54 on-demand package imports, one for each of the packages exported by the java.base module. It is as if the source file contains import java.io.* and import java.util.* and so on."

It may also be useful to separately mention that in a modular application, only public types in packages exported or opened by a module are visible outside that module and also provide the reader with a link to the tutorial on modules ( https://dev.java/learn/modules/ ).

Thanks!

[willy-b]

A section higher up in the same page ( https://dev.java/learn/packages/ (archived as is at https://web.archive.org/web/20260527153107/https://dev.java/learn/packages/ ) )
that gives the same listing (but without numbering) would also need to be updated the same as described above.

That is, in addition to the update described above,
separately under "Using Package Members"

To use a public package member from outside its package, you must do one of the following:

• Refer to the member by its fully qualified name
• Import the package member
• Import the member's entire package

is also recommended to be updated to include a 4th point

• [suggested] Import the entire module (all exported packages) which exports the member's package.

to be up to date with the new import module feature (JEP 511) that came out in Java 25 ( https://openjdk.org/jeps/511 ).