When changes to the project configuration are made, it is sometimes necessary to restart Eclipse before these take effect.

The ideal solution would probably be that config gets reloaded when the file is changed. But this might be hard to implements, so an easier option may be to reload the config when the project is cleaned.

Submitted by Hendrik van Antwerpen on 3 April 2017 at 23:42

This is unfortunately a design issue: we did not design the project/config system to react to changes. A configuration object is immutable and does not react to changes in the metaborg.yaml file.

If something keeps a reference to an IProject or ILanguageSpec object, which holds a reference to a config object, that config will never change until a new IProject or ILanguageSpec object is created. However, we could change these classes to read the modified date on the config file and recreate the config object when it changes.

A better design would be to have events fire when some configuration changes, and react to those events, but that is a big design overhaul.