TLDR: How do I enforce that a specific self-made plugin is loaded during a headless build?
I try to execute a headless build for a module and before the build starts, I want MPS to load a self-made MPS plugin that is not directly a dependency of the module. It seems like that during a headless build, this plugin is not loaded because my module does not directly depend on it.
My goal is to inject different runtimes for different build environments with the help of extensions and extension points.
- In the RCP and dev environment I deploy a plugin that implements the extension points for the production environment
- In headless environments (test execution and simple module build) I try to deploy a headless runtime plugin, that implements the extension points for headless environments
This strategy works fine for RCPs, development and even for the headless test run.
In the headless test run you can "load additional idea plugins" and this works fine.
I'm searching something similar for simple headless builds. Does anyone have an idea?