I just checked in some changes for plugins that I have been meaning to do for some time. Mainly, getting rid of the overriding of the equals() method to determing if 2 instances of a plugin are equivalent. Doing this is not so great and has implications to override hashCode(), which requires a lot more work than it was worth. There is now an isEquivalent() method in the Plugin interface that can be implemented to determine, to the degree the developer wishes, if the plugins are equivalent. The PluginRegistry uses this to determine if a plugin being started is equivalent to a plugin already running. The idea is to maintain an already running plugin over stopping it and starting the new one. This avoids losing events during the inbetween time.
I am still in the process of learning Eclipse, so I have not had a chance to run the limited plugin tests. They might fail. If so, I will fix the problems. I am going to start on some Watchdog stuff this week, and I plan to greatly improve the test suites around plugins, receivers, and watchdogs as well. Regarding Eclipse, I wish it would just let me edit java files and run ant builds. That is all I really want. None of this other project crap. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
