|
hello, I just downloaded the latest osmosis build, and it gives me this error ...\osmosis-latest>bin\osmosis Error: Could not find or load main class org.codehaus.classworlds.Launcher any idea how I could fix this ? thanks |
|
I found the following mistake in osmosis.bat: it references plexus-classworlds-2.4.jar but the real name is plexus-classworlds-2.5.2.jar, that solved it That didn't work for me. I changed to 2.5.2., saved and restartet but nothing changed. When I look in the osmosis.bat the spelling is correct. I have tried multiple versions of osmosis. What can I do? Thanks!
(15 Jan '16, 22:07)
immachon
Does https://github.com/SomeoneElseOSM/osmosis help? That's a fork that I created in September with some batch file changes: https://github.com/SomeoneElseOSM/osmosis/commit/c2a8a692f52b68f6cf997b7c410bf0ece9309a24 (there have been commits to osmosis since which this doesn't incorporate BTW)
(15 Jan '16, 22:29)
SomeoneElse ♦
I also have this problem, I had a hard drive crash, came to reinstall and downloaded all the latest zips. running osmosis came up with the error "Could not find or load main class org.codehaus.classworlds.Launcher" I went for an older version and it came up with a different error, strange So then I downloaded the zips that "SomeoneElse" suggested and hey presto the error disappeared. so I then cleaned out the directory and copied in the new bin from SomeoneElse, and the error reappeared. getting even stranger. So then I cleaned out the directory again, put in the latest release, and the error was still there, so then I copied in the bin from SomeoneELse and the error disappears, quite bizarre.
(03 Feb '16, 11:54)
Rossendale Gary
|
|
Does this previous question help? A quick web search for "osmosis classworlds" (without quotes) turns up lots of people asking the same question, and lots of answers. |
It would really help to know what O/S you are using. From the backward slash it looks like windows. Usually this is to do with path variables. I tend to work around this type of problem by running osmosis under windows from its own directory.
already tried that, no matter where I launch it, it cant find that class
windows 7 and no matter where I launch it, it cant find that class
usualy I temper javahome, but here it's the very exec that cant find his jar's