Repository navigation
Commit 47462c4
build: Align SDK modules to one version through sentry-bom
Gradle resolves version conflicts per module, so a build could mix SDK modules
of different versions, for example a newer sentry-android-core with an older
sentry-android-fragment that the Gradle plugin or another library pulled in.
That fails at runtime with NoSuchMethodError or the mixed versions check.
The publish conventions now add sentry-bom as a platform to every published
library module. Gradle then moves all SDK modules of a consumer to the highest
version present. Maven does not apply the dependencyManagement of a
dependency's POM, so Maven builds resolve as before. The BOM now also
constrains sentry-android-distribution, which is released with the SDK.
Refs #5105
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>1 parent 5bf00d1 commit 47462c4
2 files changed
Lines changed: 16 additions & 2 deletions
File tree
- build-logic/src/main/kotlin/io/sentry/gradle
- sentry-bom
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
19 | 22 | | |
20 | 23 | | |
21 | 24 | | |
| |||
26 | 29 | | |
27 | 30 | | |
28 | 31 | | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
29 | 35 | | |
30 | 36 | | |
31 | 37 | | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
32 | 47 | | |
33 | 48 | | |
34 | 49 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
16 | | - | |
17 | | - | |
| 16 | + | |
18 | 17 | | |
19 | 18 | | |
20 | 19 | | |
| |||
0 commit comments