-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
16
The following tests appear to have a direct dependence on a module named `testng`.
$ grep -r 'requires testng' open/test
open/test/jdk/java/util/ServiceLoader/security/test/module-info.java: requires testng;
open/test/jdk/java/lang/ModuleTests/addXXX/test/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/MethodHandles/privateLookupIn/test/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/modules/m1/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/modules/m3/module-info.java: requires testng;
While this has been the default automatic module name for TestNG 6.9.5, going forward, TestNG 7.* has an explicit declaration that the module name is `org.testng`. This is in the Automatic-Module-Name entry in the JAR Manifest.
These tests will probably need to be updated at the time we change to use TestNG 7.*
$ grep -r 'requires testng' open/test
open/test/jdk/java/util/ServiceLoader/security/test/module-info.java: requires testng;
open/test/jdk/java/lang/ModuleTests/addXXX/test/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/MethodHandles/privateLookupIn/test/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/modules/m1/module-info.java: requires testng;
open/test/jdk/java/lang/invoke/modules/m3/module-info.java: requires testng;
While this has been the default automatic module name for TestNG 6.9.5, going forward, TestNG 7.* has an explicit declaration that the module name is `org.testng`. This is in the Automatic-Module-Name entry in the JAR Manifest.
These tests will probably need to be updated at the time we change to use TestNG 7.*
- duplicates
-
JDK-8265020 tests must be updated for new TestNG module name
- Resolved