Duplicate classes across modules causes Bazel build failure

[belugabehr]

I am experiencing some friction in getting my corporate build system to upgrade to latest micrometer because of duplicate classes issue.

Duplicates in micrometer-test-1.17.0-M1.jar

Conflicts with micrometer-core-1.17.0-M1.jar:

✗ io/micrometer/core/instrument/binder/cache/package-info.class
✗ io/micrometer/core/instrument/package-info.class
✗ io/micrometer/core/instrument/step/package-info.class
✗ io/micrometer/core/ipc/http/package-info.class

Conflicts with micrometer-commons-1.17.0-M1.jar:

✗ io/micrometer/common/util/internal/logging/package-info.class

Please ensure that the micrometer-test package does not contain overlapping classes.

[belugabehr]

That is to say, the following two classes (for example) conflict with each other on the classpath:

1. https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/package-info.java
2. https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-test/src/main/java/io/micrometer/core/instrument/package-info.java

[shakuzen]

Having split packages is bad in general and we should work to resolve that. For clarification, though, do you mean your build system is having an issue when building an application that uses Micrometer as a dependency, or that you are trying to build Micrometer from source using your build system? Is this a publicly available build system (Maven, Gradle, Ant, Ivy, Bazel, etc) or something proprietary?

[belugabehr]

The former. We are currently using older versions of the libraries that do not have this overlap. Simply upgrading the micrometer dependencies in our project triggers a validation failure due to the overlapping classes. Thanks.

…

On Wed, Jan 14, 2026, 11:08 PM Tommy Ludwig ***@***.***> wrote: *shakuzen* left a comment (micrometer-metrics/micrometer#7067) <#7067 (comment)> Having split packages is bad in general and we should work to resolve that. For clarification, though, do you mean your build system is having an issue when building an application that uses Micrometer as a dependency, or that you are trying to build Micrometer from source using your build system? Is this a publicly available build system (Maven, Gradle, Ant, Ivy, Bazel, etc) or something proprietary? — Reply to this email directly, view it on GitHub <#7067 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC766E42OEEFLRTCBO6GPQ34G4HCRAVCNFSM6AAAAACRSKIONOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJSHAYTSMZRG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[belugabehr]

Bazel.

…

On Wed, Jan 14, 2026, 11:54 PM David ***@***.***> wrote: The former. We are currently using older versions of the libraries that do not have this overlap. Simply upgrading the micrometer dependencies in our project triggers a validation failure due to the overlapping classes. Thanks. On Wed, Jan 14, 2026, 11:08 PM Tommy Ludwig ***@***.***> wrote: > *shakuzen* left a comment (micrometer-metrics/micrometer#7067) > <#7067 (comment)> > > Having split packages is bad in general and we should work to resolve > that. For clarification, though, do you mean your build system is having an > issue when building an application that uses Micrometer as a dependency, or > that you are trying to build Micrometer from source using your build > system? Is this a publicly available build system (Maven, Gradle, Ant, Ivy, > Bazel, etc) or something proprietary? > > — > Reply to this email directly, view it on GitHub > <#7067 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AC766E42OEEFLRTCBO6GPQ34G4HCRAVCNFSM6AAAAACRSKIONOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJSHAYTSMZRG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[shakuzen]

This is one piece of fixing this: #7071

[shakuzen]

Some of the conflicts you mention seem to have existed since at least Micrometer 1.8.7 (e.g. see https://github.com/micrometer-metrics/micrometer/pull/3200/changes#diff-a84f7fb502b449057a5751a1ec3813535cfd6fb6c3fa2dfb7de70ee0a44b02cc). Are you upgrading from an earlier version than that?

[belugabehr]

Hello, Thanks again for the assistance. We are only a few versions out of date, not all the way back to 1.8. I was able to make the upgrade work, but it wasn't so simple as just updating dependencies. Just something to flag in trems of usability, but not a blocker. Thanks!

…

On Thu, Jan 15, 2026, 3:38 AM Tommy Ludwig ***@***.***> wrote: *shakuzen* left a comment (micrometer-metrics/micrometer#7067) <#7067 (comment)> Some of the conflicts you mention seem to have existed since at least Micrometer 1.8.7 (e.g. see https://github.com/micrometer-metrics/micrometer/pull/3200/changes#diff-a84f7fb502b449057a5751a1ec3813535cfd6fb6c3fa2dfb7de70ee0a44b02cc). Are you upgrading from an earlier version than that? — Reply to this email directly, view it on GitHub <#7067 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC766EYYDM2LQZCVFDBAUQD4G5GWVAVCNFSM6AAAAACRSKIONOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJTGU3DAOBYHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>