-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
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
Hard dependency on okhttp, osgi? #404
Comments
Because Moneta is still backward-compatible with Java 8. Maybe 1.5.x could raise the bar to Java 11, but for now it's still Java 8. Also the JDK HttpClient is less powerful than OkHttp, e.g. it just offers a single Jakarta Annotations are used for the |
Thanks, ok, I see the reasoning... Hard pass from me due to the above issue at this point, but if you want this library to be truly versatile and non-intrusive, please consider removing Jakarta EE requirements (so it is useful in Micronaut, Helidon SE, Spring) and prefer core Java SE over external libraries. Maybe a smaller core that can be useful by anyone, with Jakarta EE entanglements in a higher layer? |
It's a standard library that was refactored from |
While the dependency on jakarta.annotation-api is not very problematic, the dependency on okhttp is (these libraries do not have versions as OSGi bundles). Why the need to introduce this dependency from version 1.4.3, it was not there before? I cannot reopen this issue, should I create a new one for this problem? |
If read the POM correctly moneta-core has hard (compile) dependency on okhttp? What is the reason for a this (java has its own Java http client API since Java 11). Also not sure why are Jakarta Annotations also used? Some OSGI?
The text was updated successfully, but these errors were encountered: