no JAR yet.. - Githubissues

comidan / ingsw-project

Sagrada is the online multiplayer board game version of the original board game from Cranio Creations, made as Software Engineering Project at Politecnico di Milano

2 stars 0 forks source link

no JAR yet.. #8

Closed ingconti closed 6 years ago

comidan commented 6 years ago

JARs has already been built we are just waiting to upload the final release, as per indications before 8 July, if there are new indications regarding publishing date we didn't saw them, checking now if new indications have been told

ingconti commented 6 years ago

what you aswered has sense, but:

try early to prevent future problems
experiment uploading to verify final jar filesizes are fine
let us verify you DO have a working JAR

anyway is up to you... but being proactive is better.

comidan commented 6 years ago

I understand, added non final JARs right now.

ingconti commented 6 years ago

ps written a doc on Beep. so pls follow those indications.

ingconti commented 6 years ago

I did try to downloand and run it works, but:

a) ~ ingconti$ java -jar /Users/ingconti/Downloads/LM34.jar Jul 04, 2018 6:25:27 PM it.polimi.ingsw.sagrada.GameServer main SEVERE: Could not initialize dynamic class loading service Jul 04, 2018 6:25:27 PM it.polimi.ingsw.sagrada.database.SQLiteDatabase connect SEVERE: Fatal DB error : path to '/Users/ingconti/resource/database/Sagrada.db': '/Users/ingconti/resource' does not exist SQLite database connection initialized

b) If I kill server, and client is at login, you got:

SEVERE: Connection refused (Connection refused) localhost:49152 not responding, retrying in 3 seconds...

c) pls read messages:

anyway you are on the right track ..

comidan commented 6 years ago

Thank you for your detailed report.

As soon as possible I'll commit more stable JARs and finally the final one.

Regarding your report :

In point a : I tried starting a Jar using an OSX VM but didn't get this error, seems like the JAR is searching the auto extracted resource folder in the upper directory for some reasons, looking forward to fix it.

In point b : yes it is normal, I mean the client thinks he should try reconnecting : if you prefer I can set a timeout which when goes to 0 I just close the client without retrying reconnecting.

In point c : I'm very sorry!

ingconti commented 6 years ago

a)ok, is an annoying (wrong!?)message. b) use logic You already used in other parts. (do not re-invent wheel :) ) c) You are welcome