Make muzzle task depend on instrumentation project runtimeclasspath

[pavolloffay]

Signed-off-by: Pavol Loffay p.loffay@gmail.com

This is related to #1225. See the hacks what I did in regards to runtime classpath of the plugin. Maybe the plugin could expose a setting to configure javaagent-tooling and javaagent-bootstrap classpath (a similar what bytebuddy plugin does

opentelemetry-java-instrumentation/gradle/instrumentation.gradle

Line 36 in ee0e0a9

classPath = project(':javaagent-tooling').configurations.instrumentationMuzzle + configurations.runtimeClasspath + sourceSets.main.output

)

I am using muzzle plugin in my custom OTEL agent build. There are a couple of hacks that I had to make:

• copy buildSrc to my project (obvious and ugly!)
• define javaagent-tooling and javaagent-bootstrap subprojects that pull in appropriate OTEL artifacts
• move my instrumentation classes to io.opentelemetry.instrumentation. Make muzzle reference creation package(s) configurable #1395
• set correctly classpath in bytebuddy plugin (instrumentationMuzzle)

With all this I was able to run muzzle task and properly generate instrumentationMuzzle. However the build was passing only after ./gradlew assemble. Running ./gradlew clean muzzle was always failing. The following fixed the build on a clean project.

[iNikem]

Maybe the plugin could expose a setting to configure javaagent-tooling and javaagent-bootstrap classpath

This is the great idea! If we set required classpaths externally, then we can easily do #1225