Add Java 17 to Java 21 LTS Upgrade Plan with MVP Test Coverage by devin-ai-integration[bot] · Pull Request #18 · jack-killian/Deere_OperationsCenterAPI-OAuth2-Java · GitHub
Skip to content

Add Java 17 to Java 21 LTS Upgrade Plan with MVP Test Coverage#18

Closed
devin-ai-integration[bot] wants to merge 1 commit into
masterfrom
devin/1769044272-java21-upgrade-plan
Closed

Add Java 17 to Java 21 LTS Upgrade Plan with MVP Test Coverage#18
devin-ai-integration[bot] wants to merge 1 commit into
masterfrom
devin/1769044272-java21-upgrade-plan

Conversation

@devin-ai-integration

Copy link
Copy Markdown

Summary

This PR adds a comprehensive documentation file (docs/JAVA_21_UPGRADE_PLAN.md) that outlines the step-by-step process for migrating the application from Java 17 to Java 21 LTS. The document includes:

  • Pre-upgrade steps: Environment preparation, codebase review, and dependency audit
  • Configuration changes: Specific updates needed for pom.xml, .java-version, and GitHub Actions workflow
  • Dependency verification: Compatibility analysis for all current dependencies (Javalin, SLF4J, Guava, Unirest, Mustache, maven-shade-plugin)
  • MVP test coverage plan: Detailed test recommendations covering OAuth2 flows, API integration, build/runtime, web server, and dependency compatibility
  • Rollback plan: Immediate and staged rollback procedures with trigger conditions
  • Post-upgrade validation: Checklist and monitoring recommendations

This is a documentation-only PR - no code changes are included.

Review & Testing Checklist for Human

  • Verify the dependency compatibility claims are accurate (I researched via documentation/release notes but did not perform hands-on testing)
  • Review the configuration change instructions in the "Configuration Changes" section to ensure they match the actual file structure
  • Confirm the MVP test coverage plan aligns with team priorities and testing standards

Notes

The line number references in the document (e.g., "Application.java lines 62-67") are based on the current state of the codebase and may need updating if the source files change.

Link to Devin run: https://app.devin.ai/sessions/db6e374a19d545c9909619244f7e7df2
Requested by: Jack (@jack-killian)

This document provides a detailed upgrade plan including:
- Pre-upgrade steps and environment preparation
- Configuration changes for pom.xml, .java-version, and CI workflow
- Dependency verification for all current dependencies
- MVP test coverage plan covering OAuth2 flows, API integration,
  build/runtime, web server, and dependency compatibility tests
- Rollback plan with immediate and staged rollback procedures
- Post-upgrade validation checklist and monitoring recommendations

Co-Authored-By: Jack <jack.l.killian@gmail.com>
@devin-ai-integration

Copy link
Copy Markdown
Author

@devin-ai-integration

Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants