Have Spoofax services throw SpoofaxException instead of MetaborgException
When using the Spoofax API, almost everything is Spoofax-branded:
ISpoofaxAnalyzeUnit, except for
MetaborgException. I know it makes sense from the architecture perspective, but it is confusing from the user perspective.
I was asked by a user:
What is Metaborg?
It is clear, what Spoofax is. So far, website and documentation do not answer the question, what Metaborg is. I know there is JavaDoc API documentation, but even this does not explain what Metaborg is. Also, Spoofax is the brand used to sell the Metaborg layer.
Same holds for the log message
DEBUG org.metaborg.core.MetaBorg - Closing the MetaBorg API
From a user perspective,Submitted by Guido Wachsmuth on 7 September 2016 at 10:59
Closing the Spoofax APIwould make more sense.