You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace manual JDK path construction with official setup-java step
outputs. This eliminates brittle path patterns and OS-specific logic.
Changes:
- Add step IDs to all setup-java actions
- Use step outputs via env variables in .envrc creation
- Replace separate Unix/Windows steps with single unified step
- Remove architecture detection and RUNNER_TOOL_CACHE path patterns
Benefits:
- More reliable: Uses official actions/setup-java API
- Simpler: Reduced from ~60 lines to ~26 lines
- Platform-agnostic: Works on Linux, macOS, Windows automatically
- Maintainable: No hardcoded paths that break with tooling updates
Tested locally with 'act' tool.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Introduced in the course of support-and-care/maven-support-and-care#137
0 commit comments