Fix Java version compatibility and add build verification infrastructure

[Copilot]

Overview

This PR addresses a critical build failure in the asset-manager project and adds infrastructure to help users verify that all sample projects build successfully.

Problem

The asset-manager project was configured to use Java 21, but most CI environments and user setups have Java 17 available. This caused the build to fail with:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.13.0:compile (default-compile) on project assets-manager-web: Fatal error compiling: error: release version 21 not supported

Changes Made

1. Fixed Java Version Compatibility

• Updated asset-manager/pom.xml to use Java 17 instead of Java 21
• This ensures compatibility with standard Java 17 runtime environments
• All Maven projects now build successfully

2. Added Build Verification Script

• Created build-all.sh script that builds all Maven-based sample projects
• Provides clear success/failure reporting for each project
• Shows Java version information for debugging
• Returns appropriate exit codes for CI/CD integration

3. Enhanced Documentation

• Updated main README.md with build instructions
• Added Java version requirements (Java 17 or later)
• Documented the new build verification script

Testing

All Maven projects now build successfully:

• ✅ mi-sql-public-demo
• ✅ rabbitmq-sender
• ✅ todo-web-api-use-oracle-db
• ✅ asset-manager (fixed)

Users can now run ./build-all.sh to verify their environment is properly configured.

Impact

These changes make the repository more robust and user-friendly by ensuring all migration samples work out of the box and providing clear build verification tooling.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.