Preserving ResourceDescriptionsData and Boost the First Build

[bytedango]

Hi! I'm working on enhancing the building process of my language server and would like to see if I could save my index state onto the disk and load it upon opening the project, such that the first build could be somewhat faster.

For most of my DSLs, the definition area is separated from the body area, just like how Pasacal does. My build process can therefore be devided into three parts -- 1. build the definition area for ResourceDescriptions and EObjectDescriptions 2. reference the body area based on the EObjectDescriptions (I generate some metadata and hook them using an adapter onto the EObjects created) and 3. validation, etc.

Saving the index will enable, I shall assume, the removal of the first phase by loading the saved ResourceDescriptionData back to the memory, and I can update the index using delta afterwards. I would like to ask if there's a way for me to get the goal achieved. I'm currently still on Xtext 2.25 tho.

[szarnekow]

You can work with a custom ProjectManager where you deserialize the index at startup or for the initial build and save it on demand after doBuild