This message was deleted.

To me it is pretty unclear what you did and what happened. Mind providing an MCVE?

fair enough, i'll create something. it looks like i'm hitting: https://stackoverflow.com/questions/56778523/gradle-5s-gradle-api-uber-jar-puts-unwanted-slf4j-binding-on-our-classpath-cau?rq=1

Still hard to say without concrete example. The Gradle api jar shouldn't be a problem, as iirc it usually is just a

compileOnly

dependency. On the other hand, if you depend on a library that transitively depend on a concrete logging implementation like

logback-classic

or

log4j-core

that is anyway a bug in that library as no library ever should have such a dependency as the end product decides what logging framework to use.