search

RutledgePaulV / clj-okhttp

MIT License
4 stars 1 forks source link

Reflection warnings in ssl.clj #2

Closed vincentjames501 closed 2 years ago

vincentjames501 commented 2 years ago

When loading the clj-okhttp.core namespace in our project, we're getting the following:

Reflection warning, clj_okhttp/ssl.clj:37:26 - call to method generateCertificate can't be resolved (target class is unknown).
Reflection warning, clj_okhttp/ssl.clj:37:26 - call to method generateCertificate can't be resolved (target class is unknown).
Reflection warning, clj_okhttp/ssl.clj:83:5 - call to method generatePrivate can't be resolved (target class is unknown).
Reflection warning, clj_okhttp/ssl.clj:87:5 - call to method generatePrivate can't be resolved (target class is unknown).
Reflection warning, clj_okhttp/ssl.clj:90:3 - reference to field close can't be resolved.
Reflection warning, clj_okhttp/ssl.clj:107:35 - call to method generateCertificates can't be resolved (target class is unknown).
Reflection warning, clj_okhttp/ssl.clj:107:25 - call to method toArray can't be resolved (target class is unknown).
vincentjames501 commented 2 years ago

Additionally, bumping jsonista will resolve a few w/in their library!

RutledgePaulV commented 2 years ago

Sounds good. Certainly I don't want any reflection warnings in clj-okhttp. I have also been thinking about moving the ssl namespace out into a separate library and just referencing it here.

vincentjames501 commented 2 years ago

@RutledgePaulV , I think that namespace is super handy! Especially if you don't want to merge the :insecure? option 😉.

RutledgePaulV commented 2 years ago

Fixed in https://github.com/RutledgePaulV/clj-okhttp/pull/18