[osmosis-dev] Plugins

[marcus.wolschon at googlemail.com]

On Wed, 28 Jan 2009 23:07:55 +1100, Brett Henderson <brett at bretth.com>
wrote:
> Jochen Topf wrote:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE plugin PUBLIC "-//JPF//Java Plug-in Manifest 1.0"
>> "http://jpf.sourceforge.net/plugin_1_0.dtd">
>> <plugin id="geofabrik-osmosis-plugins-osmdb" version="1.0.0"
>> class="de.geofabrik.osmosis.plugins.osmdb.OsmdbPlugin">
>> 	<requires>
>> 	    <import plugin-id="com.bretth.osmosis.core.plugin.Core"
>> 	    reverse-lookup="false"/>
>> 	</requires>
>> 	<runtime>
>>         <library id="osmdb_osmosis_plugins"
>>         path="osmosis-plugin-osmdb.jar" type="code"/>
>>         <library id="osmosis" path="osmosis.jar" type="code"/>
>>         <library id="jpf" path="jpf.jar" type="code"/>
>>   
> On a semi-related issue, do these jar file names have to match exactly?  
> The ivy jar resolver is currently naming jars with their version in the 
> name.  Will this break the plugins?  I can change the ivy config to use 
> bare jar names, I only included versions because it's easy to tell what 
> versions are being used and because that seems to be the standard 
> convention.

These references are only about jar-files in the same zip-file as the
plugin. Actually osmosis.jar and jpf.jar should not be required as they
are loaded through the parent-classloder=the one that loaded osmosis
itself. But I'll have to test that.

Marcus