Commit 26d8708
Build: Add kotlin-metadata-jvm override for dependency analysis
Force a newer kotlin-metadata-jvm onto the root buildscript
classpath so the dependency analysis plugin's ExplodeJarTask can
read Kotlin 2.4.0 metadata instead of failing with "Provided
Metadata instance has version 2.4.0, while maximum supported
version is 2.3.0".
The project's own Kotlin bump to 2.4.10 (#23086) makes every
module emit 2.4.0 metadata, which exceeds the 2.3.0 cap of the
kotlin-metadata-jvm:2.2.21 reader that dependency-analysis 3.17.0
bundles, so buildHealth's explodeJar tasks fail on the weekly CI
job.
DAGP resolves kotlin-metadata-jvm unshaded into the same
buildscript classpath configuration used here, so Gradle's ordinary
conflict resolution upgrades both to the higher version
(2.2.21 -> 2.4.10). Pinned to this project's own Kotlin version so
it never forces a newer kotlin-stdlib onto DAGP's classpath than the
project already uses elsewhere.
Interim workaround endorsed by the plugin author; removable once
upstream isolates kotlin-metadata-jvm onto its own worker classpath:
autonomousapps/dependency-analysis-gradle-plugin#1661
autonomousapps/dependency-analysis-gradle-plugin#1719
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>1 parent 3ab17e4 commit 26d8708
2 files changed
Lines changed: 13 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
7 | 19 | | |
8 | 20 | | |
9 | 21 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
239 | 239 | | |
240 | 240 | | |
241 | 241 | | |
| 242 | + | |
242 | 243 | | |
243 | 244 | | |
244 | 245 | | |
| |||
0 commit comments