[Copilot]

This updates Gradle/build tooling versions in cbeust/jcommander to current stable, compatibility-safe targets (as of 2026-09-20), after auditing wrapper, build scripts, and CI version sources.
Only versions that are actually used and resolvable in this project configuration were changed.

• Version-source audit

  • Reviewed gradle/wrapper/gradle-wrapper.properties, build.gradle.kts, and GitHub workflow files for Gradle/build-plugin version declarations.

• Gradle wrapper update

  • Bumped wrapper distribution from 9.2.1 to 9.7.1 (latest stable compatible with the project’s Java baseline).

• Build plugin alignment (compatibility-preserving)

  • biz.aQute.bnd.builder remains 7.4.0 (already latest stable).
  • org.openrewrite.rewrite remains 7.39.0 because newer plugin releases require transitive artifacts not resolvable via the repository set currently configured by this build; no repository policy changes were introduced in this PR.

# gradle/wrapper/gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-9.7.1-bin.zip

[mkarg]

@copilot Fix this:

./gradlew test

[Incubating] Problems report is available at: file:///home/markus/git/jcommander-4.0/build/reports/problems/problems-report.html

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

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/9.7.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

[Copilot]

@copilot Fix this:

...

Fixed in commit 57a7467.

I removed the Gradle 10-deprecated Kotlin DSL usages in build.gradle.kts (extra delegated property and tasks.registering delegated task properties). I verified with:

• ./gradlew test --warning-mode all
• ./gradlew test

Both now run without the "Deprecated Gradle features were used" warning banner.