Problem Statement
The plugin uses component metadata rules to add dependencies if other modules are present.
This is a great tactic, but the problem is, that the plugin only supports being applied on projects, not on settings.
If you apply other plugins in settings that add component metadata rules there,
or have explicit rules in your settings script,
your plugin will take those out of service.
If the rules mode is set to fail on project rules, it even will break the build.
Solution Brainstorm
Support being applied as settings plugin and register the component metadata rules there instead of on the project dependencies.
Problem Statement
The plugin uses component metadata rules to add dependencies if other modules are present.
This is a great tactic, but the problem is, that the plugin only supports being applied on projects, not on settings.
If you apply other plugins in settings that add component metadata rules there,
or have explicit rules in your settings script,
your plugin will take those out of service.
If the rules mode is set to fail on project rules, it even will break the build.
Solution Brainstorm
Support being applied as settings plugin and register the component metadata rules there instead of on the project dependencies.