Proposal
On Upgrading from Beta.32 to Beta.33 I now get a FatalStartupException
Reproduction steps
I am using wiremock-standalone only
On Startup I now received the following exception
com.github.tomakehurst.wiremock.common.FatalStartupException: No suitable HttpClientFactory was found. Please ensure that the classpath includes a WireMock extension that provides an HttpClientFactory implementation. See https://wiremock.org/docs/extending-wiremock/ for more information.
at com.github.tomakehurst.wiremock.extension.StaticExtensionLoader.couldNotFindSuitableImplementationException(StaticExtensionLoader.java:96)
at java.base/java.util.Optional.orElseThrow(Optional.java:403)
at com.github.tomakehurst.wiremock.extension.StaticExtensionLoader.pickMostAppropriateFrom(StaticExtensionLoader.java:74)
at com.github.tomakehurst.wiremock.extension.StaticExtensionLoader.load(StaticExtensionLoader.java:48)
at com.github.tomakehurst.wiremock.extension.Extensions.configureHttpClient(Extensions.java:193)
at com.github.tomakehurst.wiremock.extension.Extensions.load(Extensions.java:132)
at com.github.tomakehurst.wiremock.core.WireMockApp.<init>(WireMockApp.java:128)
at com.github.tomakehurst.wiremock.WireMockServer.<init>(WireMockServer.java:84)
httpClient 5.6.1 is on the classpath and dropping back to Beta.32 resolves the problem.
References
I am wondering if it is related the switch to Bouncycastle as I noticed it mentions new modules have been created?
My hypothesis is that wiremock-standalone does not include the extra module?
Proposal
On Upgrading from Beta.32 to Beta.33 I now get a FatalStartupException
Reproduction steps
I am using
wiremock-standaloneonlyOn Startup I now received the following exception
httpClient 5.6.1 is on the classpath and dropping back to Beta.32 resolves the problem.
References
I am wondering if it is related the switch to Bouncycastle as I noticed it mentions new modules have been created?
My hypothesis is that
wiremock-standalonedoes not include the extra module?