[OSM-dev] Problem running osmosis (PluginLifecycleException)

[Brett Henderson]

Christoph Eckert wrote:
> No. I just did it the other way as it worked with osmosis 0.24 :) .
>   
That's cool.  It used to work that way, but there are more external 
dependencies now.
> I had a closer look at the osmosis shell script. So I do:
> ./osmosis-0.31/bin/osmosis --read-xml file="someosm.bz2" --node-key-value 
> place.city,place.town --way-key-value 
> highway.motorway,highway.trunk,highway.primary,highway.secondary --write-xml 
> file="basemap.osm"
>
> Now I get some class version error (see below). Is my java installation 
> messed?
>   
That type of error is usually because you're running java 1.5 or older.  
>From your previous emails you seem to be running java 1.6 which should 
be okay.  Can you double check to make sure you're still using 1.6?  If 
you are then I'm not sure what's going on ...

Brett
> Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version 
> number in .class file
>         at java.lang.ClassLoader.defineClass1(Native Method)
>         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
>         at 
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
>         at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
>         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>