We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If we move to Java 11 or 17 (see #817), probably the built-in java client would be sufficient for this library.
This would reduce the dependency graph of this project.
This would solve the issue that some consumer of the project have with the jersey client and Java-EE vs Jakarta-EE packages (see #841 or #894)
This is open for suggestions
The text was updated successfully, but these errors were encountered:
hi @jmini this is a very intresting project, do you have any idea on when it will be ready? it will surely speed up native build for the pipeline
Sorry, something went wrong.
When asking about agnostic HTTP client in Java I got following pointer:
Create an SPI and then have various implementations (like OkHttp, JDK HttpClient, Vert.x etc). Example projects doing so: Fabric8 Kubernetes Client Testcontainers OpenTelemetry
Create an SPI and then have various implementations (like OkHttp, JDK HttpClient, Vert.x etc). Example projects doing so:
This is probably what #778 is describing.
No branches or pull requests
If we move to Java 11 or 17 (see #817), probably the built-in java client would be sufficient for this library.
This would reduce the dependency graph of this project.
This would solve the issue that some consumer of the project have with the jersey client and Java-EE vs Jakarta-EE packages (see #841 or #894)
This is open for suggestions
The text was updated successfully, but these errors were encountered: