Possible to merge PR 3067 in 7.9.0

[carlosal1015]

TestNG Version

Hi there I am using java-testng-7.9.0, but with Java 17 and gradle 8.6 we have some issues. I look that #3067 fixed the issue, but I would like to make a patch (I tried without luck) from 7.9.0 tag.
I do not know if the next release 7.10.0 will fix the issue or is possible to provide a patch that we can merge to release 7.9.0 branch. Thank you.

Expected behavior

All tests passed

Actual behavior

==> Checking buildtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
:: There are 4 providers available for java-environment:
:: Repository extra
   1) jdk-openjdk  2) jdk11-openjdk  3) jdk17-openjdk  4) jdk8-openjdk

Enter a number (default=1): 3
looking for conflicting packages...

Packages (4) hicolor-icon-theme-0.17-3  java-environment-common-3-5  jdk17-openjdk-17.0.10.u7-1  gradle-8.6-1

Total Download Size:   357.65 MiB
Total Installed Size:  387.79 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 jdk17-openjdk-17.0.10.u7-1-x86_64 downloading...
 gradle-8.6-1-any downloading...
 hicolor-icon-theme-0.17-3-any downloading...
 java-environment-common-3-5-any downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
installing java-environment-common...
installing hicolor-icon-theme...
installing jdk17-openjdk...
installing gradle...
Optional dependencies for gradle
    gradle-doc: gradle documentation
    gradle-src: gradle sources
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
==> Retrieving sources...
  -> Downloading testng-7.9.0.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  911k    0  911k    0     0  1872k      0 --:--:-- --:--:-- --:--:-- 7379k
==> Validating source files with sha512sums...
    testng-7.9.0.tar.gz ... Passed
==> Extracting sources...
  -> Extracting testng-7.9.0.tar.gz with bsdtar
==> Starting prepare()...
It's recommended to build in a clean chroot
==> Starting build()...

Welcome to Gradle 8.6!

Here are the highlights of this release:
 - Configurable encryption key for configuration cache
 - Build init improvements
 - Build authoring improvements

For more details see https://docs.gradle.org/8.6/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)
Type-safe project accessors is an incubating feature.

> Configure project :
Building testng 7.9.0-SNAPSHOT

> Task :build-logic:code-quality:generatePrecompiledScriptPluginAccessors
The 'sonarqube' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started.
The 'sonar' task depends on compile tasks. This behavior is now deprecated and will be removed in version 5.x. To avoid implicit compilation, set property 'sonar.gradle.skipCompile' to 'true' and make sure your project is compiled, before analysis has started.

> Task :build-logic:code-quality:compileKotlin FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':build-logic:code-quality:compileKotlin'.
> Inconsistent JVM-target compatibility detected for tasks 'compileJava' (17) and 'compileKotlin' (11).
  
  Consider using JVM Toolchain: https://kotl.in/gradle/jvm/toolchain
  Learn more about JVM-target validation: https://kotl.in/gradle/jvm/target-validation 

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.6/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 1m 41s
27 actionable tasks: 27 executed

Is the issue reproducible on runner?

• Shell
• Maven
• Gradle
• Ant
• Eclipse
• IntelliJ
• NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

[krmahadevan]

@carlosal1015 - TestNG 7.10.0 will be released soon. We need to wrap up a few more issues. I am targetting this month end for the release.

Alternatively you can consume the SNAPSHOT version of TestNG and see if that helps.

Refer: https://testng.org/#_snapshots

See: https://oss.sonatype.org/content/repositories/snapshots/org/testng/testng/7.10.0-SNAPSHOT/

[carlosal1015]

Thank you.