Johnny Lim

I can reproduce the reported behavior with the provided test. See https://github.com/izeye/hello-micrometer/blob/micrometer-gh-3020/src/test/java/learningtest/io/micrometer/core/instrument/composite/CompositeMeterRegistryTests.java#L34-L54

I created https://github.com/micrometer-metrics/micrometer/pull/4958 to try to resolve this.

The "waiting for feedback" label doesn't seem to have worked for some reason.

I tried to reproduce it with Hazelcast 5.5.0 but got the same failure as @jonatan-ivanov got above. I was able to reproduce it with [Hazelcast 5.2.1 that GraalVM reachability metadata...

I created https://github.com/micrometer-metrics/micrometer/pull/5618 to try to resolve this.

"java.lang.NoSuchFieldException: ARTIFACT_ID" seems to have been fixed in https://github.com/hazelcast/hazelcast/commit/f2ff3be7221c81b834be723a3b08dca54ed45a39 that hasn't been released yet. See https://github.com/hazelcast/hazelcast/pull/26386

@lowasser As mentioned in the opening comment, I created this for libraries (ex. Micrometer), not for applications.

> Does your library just accept an already-constructed `Cache` instance from your users? @chaoren Yes, it's accepting prebuilt caches for metrics as follows: https://github.com/micrometer-metrics/micrometer/blob/4d9efae6b7f3635be5e99fa089eb2851f9d9ca78/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/cache/GuavaCacheMetrics.java#L54-L57 > Could the library configure and...

This seems to have been done via https://github.com/ePages-de/restdocs-api-spec/pull/261.

[0.16.5](https://github.com/ePages-de/restdocs-api-spec/releases/tag/0.16.5) that contains this change has been release-tagged on Mar 4, but it doesn't seem to have been published to the Maven central repository. @wodrobina Do you have a plan...