Repository navigation
Commit 39bbcf1
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.
Every published module now depends on sentry-bom as a platform. 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 and the root build share one isBomMember() check,
so the modules that depend on the BOM are exactly the ones it constrains.
Refs #5105
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>1 parent b05d954 commit 39bbcf1
3 files changed
Lines changed: 16 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
126 | 126 | | |
127 | 127 | | |
128 | 128 | | |
| 129 | + | |
| 130 | + | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
129 | 137 | | |
130 | 138 | | |
131 | 139 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
109 | 109 | | |
110 | 110 | | |
111 | 111 | | |
| 112 | + | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
| 118 | + | |
112 | 119 | | |
113 | 120 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
9 | | - | |
10 | | - | |
11 | | - | |
12 | | - | |
13 | | - | |
14 | | - | |
15 | | - | |
| 9 | + | |
16 | 10 | | |
17 | 11 | | |
18 | 12 | | |
| |||
0 commit comments