Launcher

[radeusgd]

Summary

To make it easier to manage different versions of enso, we want to provide a launcher script that allows the user to launch different enso versions in each project and manage versions of both enso and GraalVM that it runs on.

The launcher will be used to run the REPL, enso scripts and the language server. Its responsibility will be to select the correct version based on the current directory (based on project configuration), make sure it is downloaded and up-to-date and pass command arguments to the launched component. It must also be possible to update the launcher itself.

Value

It is easier to use enso releases. The users don't have to bother with downloading new releases from the website, but can just use the update tool. It is possible to maintain different versions of enso for different projects. It is less likely that users will launch enso using wrong version of GraalVM, as its versions will also be managed by the launcher by default.

Specification

Launcher

• Design the launcher (Design the launcher #954).
• Set-up CI for the launcher with the Native Image build (Set Up CI for the Launcher with Native Image Build #973).
• Specify how the launcher is distributed (CLI Distribution Design Discussion #987).
• Handle parsing CLI arguments for the launcher and the support for launcher plugins (Launcher CLI Arguments Parsing #995).
• Set-up automation for creating new releases (Automate Release Process on CI #980).
• Handle distribution layout and installation (Launcher Layout and Installer #1010).
• Enso version management (Enso Version Management in the Launcher #974).
• Running components through the launcher (Running Enso Components Through the Launcher #976).
• Launcher distribution uninstall capability (Launcher Distribution Uninstall Capability #1011).
• Managing projects and configuration (Simple Configuration Management in the Launcher #977).
• Handling broken releases (Handling Broken Releases in the Launcher #1075).
• Self-update mechanism (Launcher Self-Update Mechanism #975).
• Self-update fallback (Launcher Upgrade Fallback Infrastructure #1013).
• Locking components (Launcher Components Locking #1126).
• Logging service (Logging Service in the Launcher #1031).
• Improve launcher UX (Support top-level options after a command in the Launcher CLI #1039, Repairing Corrupted Installations #1052, Add ETA and Speed Estimation to Progressbars in the Launcher #1078, REPL Creates a Dumb Terminal on Windows When Run Through the Launcher #1099, Add Options for Questions in the Launcher CLI #1143, Synchronize Logging Output With Interactive Input #1188).
• Add an integrity check for downloaded packages (Verify Package Integrity in the Launcher #1154).
• Make manifest and config parsing more resilient to recoverable errors (Make Manifest And Config Parsing More Resilient #1494).
• Update the README included within the distribution (Update Launcher's README #1322).

Extending the Project Manager

• Update the project manager protocol (Update Project Manager Protocol #1149).
• Implement components management:
  • Separate the ComponentsManager and its dependencies into a library (Separate ComponentsManager into a Library #1152).
  • Improve locking mechanism (Thread-Safe Locking in Runtime Version Manager #1254).
  • Integrate the ComponentsManager with the project manager (Integrate Component Manager with the Project Manager #1153).
• Explore how the project manager can be started by the IDE (compiling it to Native Image or using some Java runtime) (Explore How the Project Manager Can Be Started by IDE #1150).
• Integrate with the logging service (Use New Logging Service in the Components #1144).
• Add a separate version field in engine's manifest (Split minimum-launcher-version for Project Manager #1323).

Acceptance Criteria & Test Cases

• The above specification has been completed.
• The launcher is tested and distributed in the CI.