> > I personal don't like the activation mechanism. I prefer to have the > 'activated' plugins in the plugin folder and to deactivate just > remove the plugins from the folder. > That is much easier to handle than to manage the plugins in the > folder AND setup them in the configuration file.
+1 > Right. In case a plugin A require a other plugin B that is not > available the plugin A will not be loaded, as far I remember. :-/ Stefan, here is my first feed back on the plugins dependencies: 1. How to specify some plugin dependencies? I assume it is using the directive in the plugin xml descriptor: <requires> <import plugin="plugin-id"/> </requires> specifies that this plugin requires the "plugin-id" code in its classpath at runtime. Is it right? But looking at the plugin framework code, the "requires" element is never parsed. Can you confirm this point please? 2. There is a addDependency(String id) method in the PluginDescriptor class, but this method is seems not to be used in Nutch code. 3. Out of scope, but if someone want to contribute: I added a direct dependency in my plugin build.xml file to the lucene-analysis plugin in order to compile it. But it would be better if this kind of dependency is automatically handled in the build-plugin.xml ant file by parsing the plugins xml descriptors. (If someone want to contribute. I'm not an ant expert, but I assume it could be easy by by writing an ant task based on the PluginManifestParser). Thanks for your comments. Jérôme -- http://motrech.free.fr/ http://www.frutch.org/
