> > I have just committed some modifications that enable to have some > > dependencies between plugins. > This mechanism already works, since a plugin use jar urls from all > dependent plugins in its own class-loader.
Ok. So, after a long private mail exchange with Stefan (thanks for your time and help stefan), it seems that these modifications are ok. Here is the final status for this plugin dependencies problem: ******************** JC: In the solution I have committed: 1. I uses the standard eclipse plugin.xml directives <requires><import plugin="plugin-id"/></requires>, so that it is always "Eclipse compliant", and it gives a way to specify the dependency using the plugin-id instead of the plugin jar files. SG: This makes sense, and I'm quite sure that this was the way I had implemented. The first version of the plugin.xml parser was dom4j based later it was portet to the normal xml api, so may this point was loose in until porting. That's why there are still not used methods. You definitely find the problem. JC: 2. I provide a way to compile plugins with such dependencies. 3. It works !!! SG: Great! :) *********************************** Here is a copy of my previous mail, if someone want to comment it: I have just committed some modifications that enable to have some dependencies between plugins. I would like to apply this mechanism to parse-ms* related plugins that both uses jakarta poi code. The idea is: instead of duplicating jakarta poi related jar in each lib directory of parse-ms* plugins, I would like to : * create a poi plugin that contains these jar files, * and to specify that the parse-ms* plugins depends (requires) the poi plugin. What do you think about it? What plugin name do you suggest for the poi plugin (simply poi, or something like jakarta-poi or lib-poi ?) Thanks for your suggestions and comments. Regards Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
