[maven-extension] Failure using the Otel Maven extension declared as an `<extension>` in `pom.xml` because the `pom.xml` of the Otel Maven extension lists dependencies even though they are bundled about opentelemetry-java-contrib

[cyrille-leclerc]

The problem seems to be the collaboration between the Gradle Shadow Plugin and the Gradle Maven Publish plugin.
We expect the Maven Publish plugin to not add as dependencies in pom.xml the dependencies that have been added to the "uber jar" by the Shadow Plugin.

I didn't find yet a path forward to fix the problem.

---

The cause seems to be related to Gradle Shadow Plugin > Publishing Shadow Jars > Shadow Configuration and Publishing

When configuring publishing with the Shadow plugin, the dependencies in the shadow configuration, are translated to become RUNTIME scoped dependencies of the published artifact.

[cyrille-leclerc]

Fixed by

• #87

@anuraaga @trask could we consider cutting a 1.6.1 release to ship the fix of this bug of the Otel Maven Extension?

[trask]

hey @cyrille-leclerc!

we have an undocumented practice of only patching for regressions, memory leaks and deadlocks (thanks for the reminder tho 😄, documenting that now: https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/4198/files)

we can always make exceptions, but try to keep those to a minimum

the normal release cadence is monthly, with the Java SDK releasing generally end of the 2nd week of the month, followed "shortly" after by Java Instrumentation and Java Contrib (shortly tends to be a few days to a week)

[cyrille-leclerc]

Thanks for the explanation, it's perfect for me.

[cyrille-leclerc]

Problem fixed in 1.7.0-alpha