Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

gradle-debian-helper/2.2 already checks if the JDK supports modules before adding the --add-opens options, but it checks the default JDK and not the one specified by JAVA_HOME, that's why it fails when OpenJDK 8 is used. __ This is the maintainer address of Debian's Java team

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

Am Mittwoch, dem 01.06.2022 um 17:36 +0200 schrieb Emmanuel Bourg: > gradle-debian-helper/2.2 already checks if the JDK supports modules before > adding the --add-opens options, but it checks the default JDK and not the one > specified by JAVA_HOME, that's why it fails when OpenJDK 8 is used. ok,

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

Am Mittwoch, dem 01.06.2022 um 15:03 +0200 schrieb Emmanuel Bourg: > The --add-opens option was introduced in Java 9, so this shouldn't cause an > issue with Java 11. What error did you get? The compiler complains about "unknown option --add-opens" when I try to rebuild kotlin in unstable.

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

The --add-opens option was introduced in Java 9, so this shouldn't cause an issue with Java 11. What error did you get? __ This is the maintainer address of Debian's Java team . Please use

Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages

Package: gradle-debian-helper Version: 2.2 Severity: serious X-Debbugs-Cc: a...@debian.org Hi, The newly added --add-opens option is only valid for OpenJDK 17. I understand that we switch to it for Debian 12 but it currently breaks all packages that are built with OpenJDK 11. I am currently in