ppalaga commented on a change in pull request #1993:
URL: https://github.com/apache/camel-quarkus/pull/1993#discussion_r517363240
##########
File path:
extensions/geocoder/deployment/src/main/java/org/apache/camel/quarkus/component/geocoder/deployment/GeocoderProcessor.java
##########
@@ -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"));
Review comment:
Your effort pays back!
##########
File path: integration-tests/telegram/pom.xml
##########
@@ -56,17 +56,18 @@
<groupId>org.apache.camel.quarkus</groupId>
<artifactId>camel-quarkus-attachments</artifactId>
</dependency>
- <dependency>
- <groupId>org.apache.camel.quarkus</groupId>
-
<artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId>
- </dependency>
Review comment:
The auditing idea was based on the assumption that the number of
<artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId>
occurrences in poms must be equal to the number of the magic log tokens. Now we
are stopping to use
<artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId> .
Yes, <artifactId>camel-quarkus-integration-wiremock-support</artifactId> is
a replacement, but probably not all mock will be HTTP, so the interested
parties (cc @llowinge ) will have to add the number of
<artifactId>camel-quarkus-integration-wiremock-support</artifactId> occurrences
to the number of
<artifactId>camel-quarkus-integration-test-support-mock-backend</artifactId>.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
