Repository navigation
feat: platform provider architecture
- JDK management is routed through a
platform.Providerabstraction; the native Windows provider is the current implementation, with SDKMAN planned as a follow-up - package restructuring:
utils/*,internal/icli,internal/models,internal/ui→internal/{cli,config,platform,native,tui,jdk,fsutil,httpclient,java} - new
jvms configcommand; theresolution_prioritysetting is retired (older config files still load, and the field is dropped on save) - version resolution: bare values — including numbers such as
17— are always versions;#Nselects a numbered row fromjvms listorjvms rls jvms switch --as_path/-pnow really switches to a JDK path; danglingJAVA_HOMElinks are replaced, and a non-symlinkJAVA_HOMEis never overwritten- JDK folders copied manually into
store(including names with spaces) can be listed, switched and removed again - catalog caching is configurable via
cache_toggle/cache_ttl, versions sort newest first, and failed downloads no longer report success - tests for
cli,config,jdk,native,platformandtui, plus.githooks/pre-commit
Upgrade notes
jvms switch 2now means JDK version "2". To activate the 2nd row ofjvms list, usejvms switch "#2"(quote it so PowerShell passes it through).jvms install 17/jvms use 17select JDK 17 again instead of treating the number as a catalog index; usejvms install "#17"for index selection.- This build is Windows-only: the native provider requires Windows, so other platforms stop with an explicit "not yet supported" message.