I think --disable-warnings-as-errors is for C++ warnings, not for java
warnings like deprecation, you can use
-Xlint:none to disable the warning.
But this will not prevent the output of deprecation message, the output is
like:
Note: Test.java uses or overrides a deprecated API.
Note: Recompile
Alright, thank you Thomas, thank you Erik!
Using JDK 19 as boot JDK does make the JDK 20 build work; I didn't know the
recommendation was to use the previous JDK as a boot JDK.
On Fri, 15 Mar 2024 at 17:55, wrote:
> The configure flag --disable-warnings-as-errors only applies to native
>
The configure flag --disable-warnings-as-errors only applies to native
compilation, where the C/C++ compiler is used. For Java compilation,
most of the source code is built using the interim javac, which is
itself built from the JDK src, so we have full control over what
warnings should or
Hi Simeon,
not a direct help, and I don't know the answer either, but I ran into
exactly the same problem today and switched to JDK 19 as boot jdk, which
proved a valid workaround.
Cheers, Thomas
On Fri, Mar 15, 2024 at 4:28 PM S A
wrote:
> Hi all,
>
> how do I disable warnings treated as
Hi all,
how do I disable warnings treated as errors during the OpenJDK 19+ build?
In order to better understand changes in behavior between OpenJDK versions,
I've been bisecting and compiling OpenJDK 19 and OpenJDK 20 in the recent
months.
One problem that I run into a lot is warnings failing
