[osmosis-dev] Problem using Osmosis (PluginLifecycleException)

Brett Henderson brett at bretth.com
Tue Nov 10 22:03:50 GMT 2009


marcus.wolschon at googlemail.com wrote:
> On Tue, 10 Nov 2009 12:24:12 +0100, "Kai Behncke" <Kai-Behncke at gmx.de>
> wrote:
>   
>> Dear Marcus,
>>
>>
>> thank you very much (and sorry for crossposting :-) ).
>>
>>     
>>> osmosis.bat /bin/osmosis both seem to be missing lib/test/jpf-1.5.jar in
>>> -cp
>>> and osmosis.jar is missing a "class-path: " -entry in it's manifest to
>>> require these jar-files if run as "java -jar osmosis.jar".
>>>
>>>       
>> Changing osmosis.bat is not the problem but how can I do an entry 
>> "class-path: " in it`s manifest (I never worked with Java before)?
>>     
>
> Changing the .bat will be enough to make it work.
>
> The manifest is something for Brett to do to make this
> easier for people.
>   
Ideally this should be automated as part of the ant build.  The manifest 
is already generated by ant, but it doesn't define a classpath inside 
it.  Does anybody know how to build a classpath list based on the jars 
contained in a directory within ant?  Once that's done it might be 
necessary to re-arrange where jars get stored so that the osmosis.jar 
and other jars all reside in a single directory ...

Brett





More information about the osmosis-dev mailing list