Summary

Once the ComponentsManager (now RuntimeVersionManager) is separated into a library (#1152), that library should be used to implement most of the new protocol requirements in the project manager.

Value

• The project manager automatically manages components to open/create projects using versions of Enso that do not have to be installed (as they'll be installed by the project manager when needed).
• The project manager can manage the basic configuration (like author.name and author.email for new projects).

Specification

• The project manager uses the component-manager library to handle the requests described in its new protocol.
• The 'user interface' of the component-manager (i.e. asking if a version should be installed or reporting progress of installation) is handled using the project manager protocol.
• The DistributionManager should be set-up in such a way that the installed components are shared between the project-manager and the launcher, i.e. a component installed using one has to be available in the other. This includes sharing the lockfiles so that the launcher and project-manager do not interfere with each other.
• The project manager should handle the configuration-related protocol messages using the GlobalConfigurationManager.
• The Project manager should start the language server as a separate Java process using the Runtime Version Manager.

Acceptance Criteria & Test Cases

• The components manager integration is tested as much as possible.
  • If possible, it would be good to emulate the releases in the same way as in the ComponentsManagerSpec and test if the protocol messages are handled correctly.
• Starting the language server should be well tested.
• If possible, progress notifications should be tested.