psx95
commented
6 months ago This is due to the inclusion of jackson-core in the upstream gcp-resources on which the module now depends.
In the upstream repo:
gradle -q dependencyInsight --dependency com.fasterxml.jackson.coreReveals that version 2.17 is being used
com.fasterxml.jackson.core:jackson-core:2.17.0
Variant apiElements:
| Attribute Name | Provided | Requested |
|--------------------------------|----------|--------------|
| org.gradle.status | release | |
| org.gradle.category | library | library |
| org.gradle.dependency.bundling | external | external |
| org.gradle.libraryelements | jar | classes |
| org.gradle.usage | java-api | java-api |
| org.gradle.jvm.environment | | standard-jvm |
| org.gradle.jvm.version | | 8 |
Selection reasons:
- By constraint
- Forced
com.fasterxml.jackson.core:jackson-core:2.17.0
\--- com.fasterxml.jackson:jackson-bom:2.17.0
+--- project :dependencyManagement (requested com.fasterxml.jackson:jackson-bom:{strictly 2.17.0})
| \--- compileClasspath
\--- com.fasterxml.jackson.core:jackson-core:2.17.0 (*)
com.fasterxml.jackson.core:jackson-core -> 2.17.0
\--- compileClasspathFound this stackoverflow which cited similar problem with jackson > v2.15.
Updated the dependency in this project to exclude jackson-core and the shadowJar task succeeded.
implementation(libraries.opentelemetry_gcp_resources) {
exclude group: 'com.fasterxml.jackson.core'
}Jackson-core seems to be accidentally added to the upstream detector, if possible, removing it from upstream would be a better long-term solution.
The dependency bumps made in PR #301 seems to have broken the
shadowJartask.This was missed since
./gradlew builddoes not trigger theshadowJartask.Investigation Done:
shadowJartask succeeds for commit@#300.Steps to reproduce
./gradlew shadowJarfails with the following error: