On Mon, 7 Apr 2025 11:11:08 GMT, Magnus Ihse Bursie <i...@openjdk.org> wrote:
> Analogous with how native warnings can be treated as errors or not using the > `--disable-warnings-as-errors` configure flag, this patch introduces a > `--disable-javac-warnings-as-errors` flag. > > The reason that this is not made part of `--disable-warnings-as-errors` is > discussed in the JBS issue, but in short, native warnings can easily occur > due to different build environment or compiler versions, while javac warnings > are platform independent and should only depend on the source code we > compile. That means that this option is basically only needed by developers > to temporary silence javac while developing new code. Apologies for bikeshedding, but why `*-javac-*`, and not `disable-java-warnings-as-errors`? I think we want to cover other Java tools, like `javadoc` as well? ------------- PR Review: https://git.openjdk.org/jdk/pull/24486#pullrequestreview-2752507795
