On Thu, 12 Mar 2026 15:36:07 GMT, Jan Lahoda <[email protected]> wrote:
> Consider these classes:
>
> package p;
> public class Lib {
> void main(String... args) {
> System.err.println("Lib!");
> }
> }
>
> and:
>
> import p.Lib;
> public class Main extends Lib {
> public void main() {
> System.err.println("Main!");
> }
> }
>
>
> Note the classes are in different packages. Running this on JDK 26 yields:
>
> $ jdk-26/bin/java Main.java
> Lib!
>
>
> that is not correct - the method `Lib.main(String[])` is package private, and
> is not inherited to `Main`, i.e. not a member of `Main`, and hence the
> launcher should not use it. The launcher should only inspect methods that are
> members (direct or inherited) of `Main`.
>
> This PR fixes that by only using package-private methods in they are declared
> in the same class as is the main class. Testing is enhanced to cover all
> related cases I/we were able to find.
The way the launcher figures out what method to invoke is independent of the VM
these days.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/30221#issuecomment-4052985347
