javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1247271009
Yes, I believe it can be closed, thank you for all your help!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1246035234
@ppalaga I just submitted a PR, and later I'll work on
`camel-quarkus-jcache-caffeine` and maybe other caches like Hazelcast and
EHcache too.
--
This is an automated messag
javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1245700678
OK, I made some changes:
- I added your `ServiceProviderBuildItem` so the CachingProvider is now
discovered;
- I removed most of the reflection configuration but
`co
javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1245662625
Also, I didn't want to add caffeine dependency to the extension itself
because in theory it should work with any JSR107 implementation, not just
caffeine.
--
This is an aut
javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1245659381
Hmm, I tried caffeine version sync and got an error `Execution default-cli
of goal org.l2x6.cq:cq-maven-plugin:3.1.0:sync-versions failed:
java.lang.IllegalStateException: No
javaduke commented on issue #1846:
URL: https://github.com/apache/camel-quarkus/issues/1846#issuecomment-1244364198
@zbendhiba @ppalaga I sort of made jcache work in native mode, but I only
tested it with Caffeine JCache and there are some limitations - i.e. I had to
explicitly instantiate
