Incident Report 9079511: Java Language Enhancement: Disallow access to static members via object references

[Tagir Valeev]

Cool!

On Sat, Jan 24, 2026, 19:38 Archie Cobbs <archie.cobbs at gmail.com> wrote:

> Funny you should mention that... :)
>
> In JDK 26+ you will be able to do this via flags like -Werror:static
>
> See https://bugs.openjdk.org/browse/JDK-8349847 for details.
>
> -Archie
>
> On Sat, Jan 24, 2026 at 7:08 AM Attila Kelemen <attila.kelemen85 at gmail.com>
> wrote:
>
>> My $0.02: This is an easy call. The answer is that it's not worth
>>> changing because (b) this would cause legacy to to start failing to
>>> compile, which is violates Java's stellar reputation for backward
>>> compatibility, and (b) there is already a perfectly reasonable workaround,
>>> i.e. -Xlint:static -Werror.
>>>
>>
>> I'm not arguing that the original request should be implemented and break
>> existing code (bad as they are). However, this suggestion doesn't really
>> work, because javac doesn't support different sets of values for `Werror`
>> and for mere warnings. That is, I usually want to turn on almost everything
>> for `Xlint` , but I definitely don't want every warning to be an error
>> (most notably, I don't want `@deprecated` to immediately fail compilation,
>> but I want it to be reported as a warning).
>>
>
>
> --
> Archie L. Cobbs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/amber-dev/attachments/20260124/430dd96c/attachment.htm>