Skip to content

docs: add JDK resolution strategy section to README#43

Closed
simond4680-sys wants to merge 1 commit intocodejive:mainfrom
simond4680-sys:docs/jdk-resolution-strategy
Closed

docs: add JDK resolution strategy section to README#43
simond4680-sys wants to merge 1 commit intocodejive:mainfrom
simond4680-sys:docs/jdk-resolution-strategy

Conversation

@simond4680-sys
Copy link
Copy Markdown

Summary

Adds a JDK Resolution Strategy section to the README documenting how jvm resolves Java version requests via the devkitman library.

What's documented

  • Version syntax — how 17, 17!, and provider-specific IDs are interpreted
  • Tier 1 — Local Discovery — provider ordering and first-match-wins behavior
  • Tier 2 — Default Version Upgrade — open-ended requests below v21 redirect to the default LTS
  • Tier 3 — Highest Available Fallback — last-resort aggregation across all installable providers
  • Key behaviors — installed-over-download priority, lazy installation, .jvmrc support

This was derived from a thorough analysis of the devkitman JdkManager.getJdkByVersion() implementation (v0.4.3).


Warp conversation

Co-Authored-By: Oz oz-agent@warp.dev

Document the three-tier JDK resolution cascade (local discovery,
default version upgrade, highest available fallback), version syntax,
provider ordering, and key behaviors.

Co-Authored-By: Oz <oz-agent@warp.dev>
@simond4680-sys simond4680-sys deleted the docs/jdk-resolution-strategy branch May 7, 2026 20:35
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.

1 participant