I just wanted to say we've gone through such problems already in Carrot2
-- many modules depend on each other, some of them have custom build
steps. A pure ANT solution is likely to be quite ugly... But back to the
point: you can test for existence of a plugin-specific build file and
execute it if it exists. This will probably require mutable properties
and conditionals available in ant-contrib (there are pure-ant
workarounds, but they're not too pretty in the build file).
If you need anything ant-related I have a lot of experience with this
tool, feel free to ask on my private e-mail or through the list (I check
the list less frequently though).
D.
Doug Cutting wrote:
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
