Just wondering: does mvnw verify work for you in the reproducer project? I tried ./mvnw verify -Daether.conflictResolver.versionSelector.selectionStrategy=highest and it results in NoClassDefFoundError: javax/inject/Provider or NoClassDefFoundError: com/google/common/util/concurrent/SettableFuture depending on the dependency order. The error is different, however, the project still fails in the runtime.
>as no direct deps override is expected I would like to discuss this after the main case (~ different versions requested by transitives) is resolved. By the way, I just got bitten by this bug yesterday when preparing a smoke test project for my day-to-day job. Of course, I've added a workaround, however I would love Maven to resolve the deps automatically: https://github.com/Netcracker/qubership-core-base-images/pull/45/files#diff-2c51c07cc3e9dbc829b4a2ccef3b80894e1db355b5b2b1216ba0c970b21b7361R13-R21 Vladimir
