Feature: RISC-V Platform Support in SDKMAN!

[gounthar]

• I have read the CONTRIBUTING guidelines
• I've had a conversation on our community Discord server.

Feature request

SDKMAN! currently identifies RISC-V 64-bit (riscv64) architecture as an "Exotic" platform, which results in no Java candidates being available for installation. This is becoming an increasingly important issue as RISC-V adoption grows in both development and production environments.

Current Behavior

When running sdk list java on a riscv64 system, SDKMAN! returns no available versions:

================================================================================
Available Java Versions for Exotic
================================================================================
 Vendor        | Use | Version      | Dist    | Status     | Identifier
--------------------------------------------------------------------------------
No versions available for your platform at this time.
================================================================================
Omit Identifier to install default version 21.0.5-tem:
    $ sdk install java
Use TAB completion to discover available versions
    $ sdk install java [TAB]
Or install a specific version by Identifier:
    $ sdk install java 21.0.5-tem
Hit Q to exit this list view
================================================================================

I have the JDK17 open JDK by default on riscv64, and I manually installed the JDK21 by Temurin.

Requested Feature

Add proper platform identification and support for RISC-V 64-bit architecture (riscv64) in SDKMAN!, similar to how x86_64 and aarch64 platforms are handled. This would:

1. Correctly identify riscv64 as its own platform instead of "Exotic"
2. Allow listing and installation of Java distributions that support RISC-V (e.g., Bell-Soft LibericaJDK)

Justification

• RISC-V is gaining significant traction in both embedded systems and server environments
• Several major Java distributions now offer RISC-V builds
• Proper RISC-V support would make SDKMAN! more valuable for developers working on this emerging platform

Technical Details

Platform detection could be updated to recognize uname -m output of riscv64 and map it to an appropriate platform identifier rather than falling back to "Exotic".