Hi Everybody, I've made a simple but significant improvement to the way Osmosis loads tasks and plugins.
Previously there was a file called "osmosis-plugins.conf" in the config directory that listed out all the plugins to be loaded during startup. This was the way that the tasks for each individual sub-system (ie. xml, apidb, pgsql, dataset, etc) were loaded. In other words, only a single osmosis-plugins.conf file was loaded so only one could exist on the classpath. I've changed that now so that all instances of osmosis-plugins.conf on the classpath will be processed. This allows each project (and jar file) to provide its own osmosis-plugins.conf file. I've modified all projects to include their own copy, and have removed the global copy. The implication of this is that creating new plugins is as simple as creating a new jar file with your tasks, your plugin loader class, and an osmosis-plugins.conf file. Installing them is just a matter of adding the new jar to the classpath (ie. in the lib/default directory). Note that this has nothing to do with the JPF (Java Plugin Framework) support provided by Osmosis. JPF is a far more capable (and complex) system that is unchanged and will continue to be supported (although to be honest I have very little idea how it works ;-) Brett
_______________________________________________ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
