Roland Schaer

Behaviour is consistent in the sense that it uses the "exact" match if found, otherwise falls back to newest available version matching the provided version. The `@17` version is a...

Interestingly this does not happen if `sapmachine-17` is already installed. ```bash ❯ mise i java@sapmachine-17 ❯ mise use [email protected] ... OpenJDK Runtime Environment SapMachine (build 17.0.11+9-LTS) OpenJDK 64-Bit Server VM...

@mpern Agree that this might be a better solution but i assume this will be quite some effort. I'm not familiar with the java-metadata repo in detail but historic metadata...

Okey, i'm clearly in favour of having a consistent solution by normalizing the versions in rtx-java-metadata.

@mpern with PR https://github.com/jdx/rtx-java-metadata/pull/2 merged, this should be resolved now. After `mise cache clear` the command `mise ls-remote java` should show no more semantically incorrect versions.

I also tried to make sense for the reason why BackendArg is having ToolVersionOptions. Most of the time these are not populated (empty) because the backend is built when this...

Closing this as discussed and raising a new one with a less intrusive solution.

I tried installing a build of this PR but could not getting it to work properly. Plugins did not resolve as defined in the `.prettierrc` file for some reason. What...