Migrate ServiceNow, Slack, Geocoder & Telegram tests to WireMock #1993
Conversation
| @@ -50,6 +50,7 @@ ExtensionSslNativeSupportBuildItem activateSslNativeSupport() { | |||
| items.add(new ReflectiveClassBuildItem(false, true, "com.google.maps.model.Bounds")); | |||
| items.add(new ReflectiveClassBuildItem(false, true, "com.google.maps.model.LatLng")); | |||
| items.add(new ReflectiveClassBuildItem(false, true, "com.google.maps.model.LocationType")); | |||
| items.add(new ReflectiveClassBuildItem(false, true, "com.google.maps.model.GeolocationPayload")); | |||
| <dependency> | ||
| <groupId>org.apache.camel.quarkus</groupId> | ||
| <artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId> | ||
| </dependency> |
There was a problem hiding this comment.
The auditing idea was based on the assumption that the number of camel-quarkus-integration-test-support-mock-backend occurrences in poms must be equal to the number of the magic log tokens. Now we are stopping to use camel-quarkus-integration-test-support-mock-backend .
Yes, camel-quarkus-integration-wiremock-support is a replacement, but probably not all mock will be HTTP, so the interested parties (cc @llowinge ) will have to add the number of camel-quarkus-integration-wiremock-support occurrences to the number of camel-quarkus-integration-test-support-mock-backend.
There was a problem hiding this comment.
Let me think about this some more because there are probably other (better) ways of achieving this.
No description provided.