Currently, Spoofax generates .spoofax-language artifacts containing Spoofax binaries.
Projects need an addition .jar for the necessary Java binaries with Spoofax API calls.

In our case, we don’t want to expose spoofax-language artifacts to users as this would only confuse them (“what is a .spoofax-language???”). Also, we don’t want to have two artifacts for a single parser/compiler.

What we currently do is place .spoofax-language files inside .jar files, but it requires lots of hacking to make it work.
It would be nice if Spoofax could just generate a single JAR containing all the Spoofax and Java binaries.

Even if there are multiple language components with dependencies between them, it would still be nice to have the option to package them as one JAR or at least have only at most one JAR per component.

Submitted by Oskar van Rest on 21 February 2017 at 21:55