Sometimes you want a plugin to act as a library and not an application. That is, for its modules to be available at compile time and on a running node but, say, the actual runtime parameter handling and supervision of shovels to be handled by another plugin. Since we do not currently have a concept of "library plugins" or "library dependencies", this approach demonstrates one example of how some plugins can be used as libraries. |
||
|---|---|---|
| .. | ||
| rabbitmq_shovel.schema | ||