dependency management for plugins?
Hi,
I'm currently working on some rm5 plugins which wrap some internal inhouse-only-used libraries/apps into rm-operators. As these libraries partially have huge dependency trees (~30 jars) which are partially overlapping with the rm-dependencies, my question is how to deploy the plugins? Is there a way to embed the jars of the dependencies into the plugin-jar? Or do I need to mess up the rm5-lib-directory? Do i need to be careful to avoid that my plugin-dependcies mess up the class-path of RM itself?
I've noticed that for the weka-plugin, the weka.jar was simply unzipped into the extension jar. The same seems to be done for the reporting-plugin. However for more complex plugins, this approach seems to be not feasible/elegant if many dependencies are required.
I've scanned through the (partially outdated) rm4.4 docu but even if some sections (like 2.5) touched the topic, the solution is not yet clear to me.
Personally, I consider the issue of dependency management a core issue of any plugin model. Only if it is solved properly, people are likely to start to develop plugins.
Any help/hint/idea/link is welcome. :-)
Best, Holger
I'm currently working on some rm5 plugins which wrap some internal inhouse-only-used libraries/apps into rm-operators. As these libraries partially have huge dependency trees (~30 jars) which are partially overlapping with the rm-dependencies, my question is how to deploy the plugins? Is there a way to embed the jars of the dependencies into the plugin-jar? Or do I need to mess up the rm5-lib-directory? Do i need to be careful to avoid that my plugin-dependcies mess up the class-path of RM itself?
I've noticed that for the weka-plugin, the weka.jar was simply unzipped into the extension jar. The same seems to be done for the reporting-plugin. However for more complex plugins, this approach seems to be not feasible/elegant if many dependencies are required.
I've scanned through the (partially outdated) rm4.4 docu but even if some sections (like 2.5) touched the topic, the solution is not yet clear to me.
Personally, I consider the issue of dependency management a core issue of any plugin model. Only if it is solved properly, people are likely to start to develop plugins.
Any help/hint/idea/link is welcome. :-)
Best, Holger