Jérôme Charron wrote:
Finaly, the more I look at the ant code for plugins the more I think we must redesign it. In the actual ant scripts, each plugin is a ant project, so there is no way to define ant dependencies between plugins. (=> if you compile a plugin A that depends on another one (B), you must manually compile B before compiling A => we loose one of the major ant benefit) I suggest to define each plugin as a target, so that we can define someting like: <target name="protocol-httpclient" depend="lib-http,lib-commons-httpclient">
This sounds good. Note that the plugin build.xml may contain some plugin-specific commands, like copying test files to the build directory, downloading third party libraries, etc. How will these be accomodated in your scheme? It seems odd to include these in the plugin.xml, since they're really build-specific...
Doug ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
