WorkerApi - avoid appending implementationClasspath to applicationClasspath


(Predrag Knezevic) #1

Hi,

I have noticed that when using Worker Deamon, implementationClasspath is always appended to applicationClasspath, i.e. on the classpath provided through WorkerConfiguration.classpath() method. It seems that plugins or script classloader have as the parent the one that holds all Gradle distribution jars, and this is somehow expectable.

Unfortunately, if I add dependency to logback for my worker, I start getting the famous Class path contains multiple SLF4J bindings warning.

The only idea I got is to create a custom classloader, load action class though it, limiting in that way the jars that are going to appear on the worker application classpath. Any better idea?