On 12/11/2015 16:44, Dimitry Sibiryakov wrote: > 12.11.2015 19:24, Adriano dos Santos Fernandes wrote: >> BTW, another info the plugin entry point could receive now: the library >> filename. >> >> This way it can load additional configuration files, for example. > It already can be done with IConfig that provides access to all > configuration a plugin > needs. There is no need in additional config files. >
Not only config file, the FB/Java plugin needs a *.jar directory. It could have a config file with a configuration for it? Sure, but it could have a default libdir/jars/*.jar as well. The design choose by Firebird code is that defaults does not need to be listed in the config file. It's all commented for core. You see here too: I can have a Java plugin module with different factories and different plugins, but I would need a single classpath entry for the whole module. Plugin module should have its optional config too, as I stated in the original message. Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
