Download errors when starting glowstone for the first time
I have been playing with Glowstone in the past without any problems. However when I try to startup the server now I get error messages while downloading some libraries: mysql-connector-java 5.1.39, slf4j jdk14 1.7.15 and sqlite-jdbc 3.15.1.
It seems the Maven repository at https://repo.glowstone.net/service/local/repositories/central/content does not have any content. Is this normal?
I need you to give me the exact errors you get.
Yes, that should appear to be empty - it’s a virtual maven repo that mirrors Maven Central.
One of the error messages is:
18:59:20 [WARNING] Failed to download: sqlite-jdbc 3.15.1 java.io.FileNotFoundException: https://repo.glowstone.net/service/local/repositories/central/content/org/xerial/sqlite-jdbc/3.15.1/sqlite-jdbc-3.15.1.jar
(The rest of the errors were blocked by the spam filter.)
Edit: to reproduce: start the glowstone server in an empty directory.
Garth Johnson last edited by
I am having the exact same issue. I notice that depending on whether I attempt to run the crossover version or latest, I get slightly different results but they all seem to be pointing at the same missing resource tree.
Hmm, okay. We’ve been having some issues with our maven repo lately (by “issues”, I mean most of the maven repo software is old, outdated, broken or archaic).
Hop on to the Discord server if you have any ideas - Archiva is our current piece of crap.
This issue should be fixed. Lets us know how you get on!
I still have the same problems, for instance a 404 error on https://repo.glowstone.net/service/local/repositories/central/content/org/slf4j/slf4j-jdk14/1.7.15/slf4j-jdk14-1.7.15.jar.
Wouldn’t it be possible to set up some static hosting for the required files?
Try it now.
No, the issue isn’t that the server isn’t working, it’s that the URLs are different and I have to rewrite them server-side.
That URL works for me now.
It now works for me as well.
Thanks for your help!
I’ll close this topic, then. Feel free to open another or ask on Discord if you run into this issue again!