ci: surface build errors in workflow

[tcheeric]

Summary

• capture Maven build output to a log file
• print build errors before the log tail on failure

Testing

• ./mvnw -q verify (fails: Network is unreachable)

---

https://chatgpt.com/codex/tasks/task_b_68a6ed11578c8331a3cf9a256362f5b6

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull Request Overview

This PR enhances the CI workflow to capture and display Maven build output for better debugging when builds fail. The change improves the visibility of build errors by capturing output to a log file and displaying relevant error information on failure.

• Captures Maven build output to a log file using tee
• Adds a conditional step to display build errors and log tail when builds fail

[Copilot]

The |& operator is a bash-specific feature that may not be available in all shell environments. Consider using 2>&1 | tee build.log for better portability across different shells.

Suggested change

	run: ./mvnw -q verify |& tee build.log
	run: ./mvnw -q verify 2>&1 | tee build.log

[Copilot]

[nitpick] The regex pattern ^\[ERROR\] assumes Maven's specific error message format. Consider making this more robust by also checking for other common error patterns or using Maven's built-in error reporting flags.

Suggested change

	grep '^\[ERROR\]' build.log || true
	egrep '^\[ERROR\]|BUILD FAILURE|Exception|Caused by:' build.log || true