mirror of
https://github.com/enso-org/enso.git
synced 2024-11-22 11:52:59 +03:00
9a49a02e3f
Fixes `--jvm` option, given to the native image. This was failing on my machine, because when given `--jvm` option, the runner was trying to find the `java` executable from the distribution manager's runtime (on my system located in `~/.local/share/enso/runtime`) and it used the first runtime found. But the first runtime on my system is JDK 17. The `--jvm` option now tries to: - Find a JDK from the distribution manager that has the same version as the JDK used for building the engine. - If there is not an exact version match, it tries to find a runtime from distribution manager that is *newer*. - If none, fallback to system-wide search - System-wide search tries to find `java` from `$JAVA_HOME` and from `$PATH`. But this is just a fallback. # Important Notes - Added test to Engine CI jobs that pass `--jvm` argument to a native image of engine-runner - |
||
---|---|---|
.. | ||
bin | ||
engine/THIRD-PARTY | ||
launcher | ||
lib/Standard | ||
project-manager/THIRD-PARTY | ||
enso.bundle.template | ||
launcher-manifest.yaml | ||
manifest.template.yaml |