Feature: Support view and download old version of corretto java

[xiaoxiangmoe]

• I have read the CONTRIBUTING guidelines
• I've had a conversation on the #cli-development Slack channel about this request.

Feature request

In github corretto-21/releases, we can download corretto java 21.0.2.14.1 and corretto java 21.0.2.13.1

But I try

sdk install java 21.0.2.14.1-amzn

it puts

Stop! java 21.0.2.14.1-amzn is not available. Possible causes:
 * 21.0.2.14.1-amzn is an invalid version
 * java binaries are incompatible with your platform
 * java has not been released yet

If we try to get all version of java

sdk list java

================================================================================
Available Java Versions for macOS ARM 64bit
================================================================================
 Vendor        | Use | Version      | Dist    | Status     | Identifier
--------------------------------------------------------------------------------
 Corretto      |     | 22.0.1       | amzn    |            | 22.0.1-amzn         
               |     | 21.0.3       | amzn    | installed  | 21.0.3-amzn           
               |     | 17.0.11      | amzn    |            | 17.0.11-amzn        
               |     | 11.0.23      | amzn    |            | 11.0.23-amzn        
               |     | 8.0.412      | amzn    |            | 8.0.412-amzn  

I can't see version of 21.0.2.14.1 and 21.0.2.13.1

If we try to download it

sdk install java 21.0.2-amzn

it will get Corretto-21.0.2.13.1

java --version        
openjdk 21.0.2 2024-01-16 LTS
OpenJDK Runtime Environment Corretto-21.0.2.13.1 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Corretto-21.0.2.13.1 (build 21.0.2+13-LTS, mixed mode, sharing)

Question

1. Can we view all version of corretto java?
2. Can we download both corretto-21.0.2.13.1 and corretto-21.0.2.14.1

[SPONGE-JL]

I strongly agree with this issue. In my experience, SDKMAN's only weakness is that when a machine or team member changes before SDKMAN covers a new version, projects with strict version upgrade procedures simply stop working.

[SPONGE-JL]

Additionally, precise specification and download of sub-minor versions is crucial. Loose version resolution sometimes makes it difficult to have confidence during debugging. When troubleshooting production issues, we need to be
absolutely certain that our local environment matches the exact version running in production—down to the patch level.

Security is another concern. Upstream vendors often release critical security patches that take days or weeks to appear in SDKMAN's central repository. During this gap, teams are forced to choose between staying on a vulnerable version
or abandoning SDKMAN entirely for manual installation.

Allowing users to register custom versions or specify direct download URLs would make SDKMAN more resilient and enterprise-ready, without compromising its simplicity for typical use case