This message was deleted.

You show it is in your

runtimeClasspath

, but is it in your

compileClasspath

? I guess you are using a transitive dependency - which is bad practice - and updated Gradle to a version where most transitive dependencies do not pollute your compile classpath anymore which for example also makes compilation faster.

Thank you for the solution. I solved this issue by using

api

instead of using

implementation

for the transitive dependency.

You really shouldn't do that, unless the library is really used in the API of that module, that is as parameter type, return type, super class, ... of public API. If it is just part of your private API or method implementations, it is - as I said - bad practice to use it from a downstream project and that should declare its dependency itself explicitly.

Sure I got your point.