Hi Sunburned, Plugins are hard enough to write. I don't think we should add additional requirements. Besides, you method does nothing for all existing plugins unless they are rewritten. Another solution is to simply have an XML file be present for each plugin that lists the major classes that it depends on. The plugin loading code in the core can then be modified to load the X<: file, use reflection to determine if the dependent classes are available, log an appropriate error message, and refuse to load the plugin if the dependencies are not present. We can either make the XML file optional since simple plugins don't usually have extra dependencies outside the normal libraries.
regards, Larry On 2/22/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote: > I've added some more thoughts about supporting plug-in dependencies to my > blog: > > http://openjump.blogspot.com/ > > SS > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > -- http://amusingprogrammer.blogspot.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
