Declare a dependency with a specific version within pom.xml whilst simultaneously banning that same version - Does this make any sense?

[dfreismuth]

At least Gradle seems to get confused within dependency resolution, you include e.g. 'reactor-core' whilst also banning the library with the same version. Does this make any sense? I am not experienced with pom bannedDependencies so I might simply not got the Idea behind this...

See example taken from main/sdk/core/azure-core/pom.xml:

<dependency> <groupId>io.projectreactor</groupId> <artifactId>reactor-core</artifactId> <version>3.4.41</version> <!-- {x-version-update;io.projectreactor:reactor-core;external_dependency} --> </dependency>

and later within the same file:

<bannedDependencies> <includes> <include>io.projectreactor:reactor-core:[3.4.41]</include> ...

[alzimmermsft]

Hi @dfreismuth, the configuration you've shared is a bit confusing, but this is more on the configuration names of maven-enforcer-plugin names being confusing where includes mean this dependency is allowed and excludes means this dependency isn't allowed.

So, what that configuration is stating is that only version 3.4.41 of io.projectreactor:reactor-core is an allowed dependency in our projects.