mgbowman

> And the (I suppose, correct) conclusions by Mathew I've dug deeper and even if I remove the reference to `HttpClientFactory` (and just instantiate `HttpClient` myself), I still get the...

If `TrustManagerProvider` is deprecated (I'm assuming in favor of `ExtensibleTrustManager`), why are the reference calls to `setExtensibleTrustManager` / `unsetExtensibleTrustManager` marked as `@Deprecated` (instead of the calls to `setTrustmanagerProvider` / `unsetTrustmanagerProvider`)?...

Sorry 🤦‍♂️

> Nonetheless, this warning is usually just a warning that can be ignored and SCR still manages to bring all components up. There's one user reporting that the binding stops...

Just another data point... if I run OH2 with `org.eclipse.smarthome.io.net` from within my workspace (vs. the target platform), the circular dependency warning goes away.

I need to get a proper ESH dev env setup but I could reproduce it consistently like this... `FooThingHanderFactory.java` ``` @Component(service = ThingHandlerFactory.class, configurationPid = "binding.foo") public class FooThingHandlerFactory extends...

@maggu2810 I'm not exactly sure (the code looks good to me), but note what I said before: > Just another data point... if I run OH2 with org.eclipse.smarthome.io.net from within...

This looks pretty straight forward to me. Any chance we can get this into the next release?

@andreynering @pd93 sorry to nag but my org could _really_ use this functionality right now. Any chance one of you guys could review / comment on this?

Awesome 🚀 When can we expect an official release containing this new experiment?