On Mon, 2003-10-20 at 15:40, Mark Womack wrote: > 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. >
+1, good move. > 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. > > 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, for testing purposes I just run Ant in a command line window. I was also thinking of creating a sort-of-MegaTestSuite class that creates a TestSuite object encapsulating the tests that are run in Ant so that it can easily be run inside Eclipse. Feel free to email me offline for any Eclipse questions, been using it for quite a while now and loving it. Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
