This points out an important deficiency in the plugin system - currently it is not possible to be absolutely sure which plugin runs first. Many Unix systems solve this by naming (e.g. /etc/rc.d scripts are named like "S01xxx.sh", "S02xxx.sh") - we could do it that way... It would also be possible to put a "priority" number in the plugin definition, so that the plugins are ordered during execution according to their "priority".
I like the idea of a priority number in the plugin definition.
I think using naming for priority is the most easiest and fault tolerant solution.
I flowed a set of discussion in other projects about this issue and in the end they use naming conventions since that has a set of benefits.
In case we have prorities in the plugin.xml file then to change the plugin.xml is required for each installation.
It can easy happen that two plugins have the same priority number.
In case we use the folder name solution it is not possible that we have 2 folder with the same names.
So I vote for Andrzej's suggestion.
Stefan
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Nutch-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nutch-developers
