This message was deleted.

I don't think so. If you build a bad-practice fat jar and have no duplicte strategy defined, you get a complaint. If you have one defined it is used. The thing the enforcer plugin checks is, that a class is not present in multiple of the dependencies because for example multiple libraries made the bad decision to shade dependencies and even without relocation. So the same problem can exist in Gradle. Circular dependencies during modules that are built should be prevented by Gradle. But library A that depends on library B while library B depends on library A is probably still possible even though architecturally questionable. You might be interested in the http://kordamp.org/enforcer-gradle-plugin/ plugin, specifically the

BanDuplicateClasses

rule. The

BanCircularDependencies

is not ported it seems.

thanks dear