On 24.08.2011 10:04, Rahkonen Jukka wrote: > Hi, > > It looks like plugins may become non-operational during the time. Perhaps we > could add a table into the wiki with fields like > Plugin name / Download URL / Document and manual URL / Wiki URL / Screenshots > / Tested with (JRE, OpenJUMP version) / Known issues / Active or not (can the > author be contacted) > > The lib\ext directory comes also pretty messy with many installed plugins. Is > it possible to place the files which are needed for a certain plugin into a > subdirectory? It would help in removing and updating plugins. >
a note like 'verified for oj version x.x' could help, but who is going to maintain the list? nobody really uses all plugins. regarding subdirectories. no extension jars have to stay in lib/ext. my extensions use a custom classloader that enables them to look for their libraries themself, so i could put them into subfolders. allowing oj to search recursively into subfolders would disrupt these extension as they use the same libraries, but versioned differently. my suggestion would be to add the classloader to oj. actually i loosely plan this since it is quite stable, but in connection with a new plugin manager as discussed here http://www.mail-archive.com/[email protected]/msg08953.html alas, i don't have no idea when to do it ;) i could have a look if it would be possible to implement only the classloader so that e.g. extension foobar in a file foobar-1.0.jar would look in a subfolder 'foobar-1.0' for further jars to load. comments? ede ------------------------------------------------------------------------------ EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
