Prefer distribution/lib/Standard files when runEngineDistribution

[JaroslavTulach]

Pull Request Description

Prefer distribution/lib/Standard/* files over the files in built-distribution/enso-engine-*/enso-0.0.0-dev/lib/Standard/. This solves the common error when one debugs thru files and edits them just to find out they are rewritten by next build.

Important Notes

The support for locating alternativeFile is only enabled for developers. E.g. when Enso version is 0.0.0-dev. This is satisfied when one uses:

enso$ sbt
sbt:enso> runEngineDistribution --run test/Base_Tests --debug

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Java,
• Debugging was manually tested

[JaroslavTulach]

The following picture show that while stepping thru the standard libraries...

• the distribution/lib/Standard versions are loaded
• they have the Git history associated
• editing them will update the "right" sources
• running runBuildEngineDistribution updates the build-distribution as usual
• the same support works in VSCode

[Akirathan]

Do I assume correctly that this also works for enso --inspect --run ...? This will make life of Chrome devtools users easier as well - we can just load the workspace from distribution/lib ...

[JaroslavTulach]

JVM tests are hitting the assert introduced by this PR...

[Akirathan]

JVM tests are hitting the assert introduced by this PR...

That is unexpected. Clearly, CI jobs are setting ENSO_VERSION (https://github.com/enso-org/enso/actions/runs/12124001092/job/33800730744?pr=11736#step:7:132) to something else than 0.0.0-dev.

GitHub

Prefer distribution/lib/Standard files when runEngineDistribution · enso-org/enso@ff7bf8a

Enso Analytics is a self-service data prep and analysis platform designed for data teams. - Prefer distribution/lib/Standard files when runEngineDistribution · ff7bf8a

[JaroslavTulach]

Do I assume correctly that this also works for enso --inspect --run ...?

Yes, when the enso launcher is started with -ea (for example via sbt's runEngineDistribution), then even Chrome Dev tools show the sources from distribution/lib:

[radeusgd]

I cannot find the -ea check anywhere. Is this doc up-to-date?

[radeusgd]

Wow I didn't use runEngineDistribution much, but that makes me want to reconsider! This should cut the iteration time tremendously!