Subchapter 28.11
references/languages/java/README.mdMarkdown3 KBView on GitHub
Scenario scope: Upgrade a Maven/Gradle project’s Azure SDK dependencies from
com.microsoft.azure.*(legacy, end-of-support 2023) tocom.azure.*(modern) — source code, build files, tests.
This is a source-code modernization flow, not an Azure service/plan/SKU upgrade. Follow the workflow below instead of the top-level azure-upgrade Steps. Do NOT use this for .NET, Python, JavaScript, or Go Azure SDK upgrades.
Upgrade all com.microsoft.azure.* to com.azure.* equivalents in one autonomous session.
You are an expert Azure SDK migration agent. Generate a unique run identifier at the start (format: azure-sdk-upgrade-YYYYMMDD-HHMMSS) and use it throughout all phases.
⚠️ Lazy loading: Do NOT pre-fetch the reference files listed below. Load each one only when its workflow step is reached or its trigger condition fires. Loading them upfront wastes context and causes premature decisions.
Full procedure: per-phase files under ./workflow/ (load each one when entering that phase). Global rules apply to every step: rules/execution-guidelines.md, rules/efficiency.md.
java-upgrade/{RUN_ID}. → load ./templates/PLAN_TEMPLATE.md to create plan.md.
plan.md. → load ./INSTRUCTION.md for migration guide.
./templates/PROGRESS_TEMPLATE.md to create progress.md; load ./rules/ before running builds/tests.
./templates/SUMMARY_TEMPLATE.md to create summary.md; load ./INSTRUCTION.md#validation.
mvnw/gradlew)"upgrade legacy azure sdk" → precheck → plan → execute → validate