[java] remove deprecated methods from the HttpClient interface

[joerg1985]

🔗 Related Issues

Fixes #16673, there is no need for theses methods, as the JdkHttpClient does expose the client.
The basic idea behind a interface is to abstract things, so we should follow this idea.

💥 What does this PR do?

Remove the AI slop from the interface.

🔧 Implementation Notes

Only deletions, nothing added

🤖 AI assistance

• No substantial AI assistance used
• AI assisted (complete below)
  • Tool(s):
  • What was generated:
  • I reviewed all AI output and can explain the change

💡 Additional Considerations

🔄 Types of changes

• Cleanup

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📜 Skill insights (0)

1. Native request callers break on upgrade 📘 Rule violation ≡ Correctness

Description

HttpClient removes sendAsyncNative and sendNative after their deprecation named the
nonexistent JdkHttpClient#httpClient() rather than the actual client() accessor. Existing source
no longer compiles and existing binaries fail when invoking either method, while the prior warning
gave callers no valid named migration target.

Code

java/src/org/openqa/selenium/remote/http/HttpClient.java[L49-52]

-   * @deprecated use JdkHttpClient#httpClient() instead.
-   */
-  @Deprecated(forRemoval = true)
-  <T> CompletableFuture<java.net.http.HttpResponse<T>> sendAsyncNative(

Evidence

Compliance rule 1 permits public removal only after deprecation with guidance toward an alternative.
The removed declarations direct users to JdkHttpClient#httpClient(), but the current class exposes
the native client through client() at lines 152-155, so the required migration guidance was
invalid before removal.

AGENTS.md: Preserve Public API and ABI Compatibility and Follow Deprecation Policy
java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java[152-155]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The public native request methods are being removed without a valid prior migration message because their deprecation refers to a nonexistent accessor.

## Fix Focus Areas
- java/src/org/openqa/selenium/remote/http/HttpClient.java[42-69]
- java/src/org/openqa/selenium/remote/http/jdk/JdkHttpClient.java[575-586]

## Recommended Fix
Restore both methods and their implementations for another deprecation cycle, correct the deprecation guidance to reference `JdkHttpClient#client()`, and retain focused compatibility coverage until removal is permitted.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

Review mode: ⚖️ Balanced: This is a localized API cleanup, but removing public interface methods across production implementations and tests carries real compatibility and compilation risk, warranting a complete single-pass review.

Tip of the day

💡 Did you know, you can switch off images and animations for a plain-text comment

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗