This message was deleted.

Diagram somewhat illustrating the project structure we have.

Enforced platforms have been added to ease Maven to Gradle transition, as the platform then behaves more like the Maven resolution mechanism. It is however problematic and does not compose well as you have discovered. The recommended way for achieving what you want is to embrace

strictly

constraints. But this probably means copying Maven BOM content to a Gradle platform.

Thanks for your reply! What would that solution mean when Software module 1 enforces version

1

, Software module 2 enforces version

2

, and Application 1 enforces version

3

(all through a Gradle platform)? If I understand

strictly

constrains correctly, Gradle would not be able to resolve this automatically, or am I mistaken there? When transitively including a Maven BOM with

enforcedPlatform

in a Gradle platform I believe these become

strictly

constraints. Copying the BOMs we use is not really a good option as we use some pretty extensive ones!