You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "ppalaga (via GitHub)" <gi...@apache.org> on 2023/03/13 13:09:12 UTC
[GitHub] [camel-quarkus] ppalaga commented on issue #4616: camel-quarkus-hazelcast and camel-quarkus-cxf-soap in same project cannot build native image
ppalaga commented on issue #4616:
URL: https://github.com/apache/camel-quarkus/issues/4616#issuecomment-1466116213
There is indeed a conflict between ours https://github.com/apache/camel-quarkus/blob/e5ec7310ec8a1f700359745ef85f8df4f5f28ed0/extensions/hazelcast/deployment/src/main/java/org/apache/camel/quarkus/component/hazelcast/deployment/HazelcastProcessor.java#L55-L67
and quarkus-hazelcast-client's https://github.com/hazelcast/quarkus-hazelcast-client/blob/dcf253cbed800de8e4174e4a1e21a92d0a1dcde0/deployment/src/main/java/io/quarkus/hazelcast/client/deployment/HazelcastClientProcessor.java#L241 init setting for ICMPHelper.
We should try to remove the RuntimeInitializedClassBuildItem on our side and see whether it helps.
The camel-quarkus-cxf-soap interference is strange. I only see an optional provided hazelcast dependency in cxf-services-sts-core that camel-quarkus-cxf-soap does not seem to depend on in any way. Do you happen to have io.quarkiverse.cxf:quarkus-cxf-services-sts in your app?
--
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.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org