Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from repo
Assess and upgrade Azure workloads between plans, tiers, or SKUs with automated migration steps
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/languages/java/bom-migration/bom-validation.md
1# BOM Migration — Validation Checklist23After BOM migration, verify:45- [ ] Project compiles successfully.6- [ ] No legacy `com.microsoft.azure.*` dependencies remain anywhere (pom.xml, build.gradle, TOML, settings.gradle).7- [ ] BOM-managed Azure libraries have **no** explicit version (no `<version>` tag, no version string, no `version.ref`, no `.versionRef()`).8- [ ] The BOM version is correct — check against https://repo1.maven.org/maven2/com/azure/azure-sdk-bom/910## Additional checks for TOML version catalog projects1112- [ ] No orphaned entries in `[versions]` (every version key must be referenced by at least one library or plugin).13- [ ] `[bundles]` aliases match current `[libraries]` aliases (no stale references).14- [ ] `build.gradle` uses `libs.<alias>` references — no raw `"group:artifact:version"` strings for Azure libraries.1516## Additional checks for programmatic settings.gradle catalog projects1718- [ ] No orphaned `version(...)` calls (every version must be referenced by at least one `library` or `plugin` entry).19- [ ] `bundle(...)` aliases match current `library(...)` aliases (no stale references).20- [ ] `build.gradle` uses `libs.<alias>` references — no raw `"group:artifact:version"` strings for Azure libraries.21