Replying to self: it seems that warning is part of the incubator JEP
https://openjdk.org/jeps/11
and can not be suppressed. The "--add-modules" makes the API available,
but since incubator APIs are supposed to be non-final there is a
mandatory warning that an applications uses them whenever an incubator
module is resolved.
I guess we cań live with that.
Sorry for the noise,
Rainer
Am 04.05.23 um 12:40 schrieb Rainer Jung:
Hi there,
when testing TC 10.1 and 11 I get lots of
[junit] WARNING: Using incubator modules: jdk.incubator.foreign
lines in the output. This happens when testing with Java 17. Not with 11
and not with 20 or 21. Don't know about 12-16 and 18-19.
We do have a block in build.xml that adds an --add-modules and the
running java processes during the unit tests do have the following flags
set:
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
--add-opens=java.base/java.util=ALL-UNNAMED
--add-opens=java.base/java.util.concurrent=ALL-UNNAMED
--enable-native-access=ALL-UNNAMED
--add-modules jdk.incubator.foreign
Only the java launcher process, that is the parent of those two does not
have these flags set.
The count of such lines is two more than the number of test classes run.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
