Commit ea8f910
build: fail fast when a published module is missing POM_ARTIFACT_ID/POM_NAME
Recurring pain: a new gradle module without its gradle.properties publishes wrong
coordinates (artifactId defaults to the bare project name, not skainet-transformers-*)
and/or fails at the Maven Central deploy (POM_NAME required) — discovered only at
release/publish time.
The bom-coverage plugin already iterates every published subproject (to build the BOM
constraints), so add a configuration-time check there: each published module must set
POM_ARTIFACT_ID + POM_NAME, else throw a clear GradleException naming the module + the
fix. Now any build touching :llm-bom (i.e. CI) catches a forgotten gradle.properties
immediately. Verified: passes with the file, fails with a precise message without it.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent 6c548d7 commit ea8f910
1 file changed
Lines changed: 22 additions & 0 deletions
Lines changed: 22 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
40 | 62 | | |
41 | 63 | | |
42 | 64 | | |
| |||
0 commit comments