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- [ ] Re-resolve the latest stable `azure-sdk-bom` from the Azure SDK for Java source of truth and confirm the plan guideline `TARGET_AZURE_SDK_BOM_VERSION` matches it exactly.9- [ ] Every BOM version in the migrated project equals `TARGET_AZURE_SDK_BOM_VERSION`; no BOM version was copied from the original project, examples, prior plans, or model memory.10- [ ] No stale `azure-sdk-bom` version remains.1112## Additional checks for TOML version catalog projects1314- [ ] No orphaned entries in `[versions]` (every version key must be referenced by at least one library or plugin).15- [ ] `[bundles]` aliases match current `[libraries]` aliases (no stale references).16- [ ] `build.gradle` uses `libs.<alias>` references — no raw `"group:artifact:version"` strings for Azure libraries.1718## Additional checks for programmatic settings.gradle catalog projects1920- [ ] No orphaned `version(...)` calls (every version must be referenced by at least one `library` or `plugin` entry).21- [ ] `bundle(...)` aliases match current `library(...)` aliases (no stale references).22- [ ] `build.gradle` uses `libs.<alias>` references — no raw `"group:artifact:version"` strings for Azure libraries.23