Julian

since i have already launched it on that Mac using the Terminal workaround i cannot tell you if resigning helpts with the launch issue. it definitely gets rid of the "code-signature of app is invalid" message though

launch issue is probably because the signature is not just ad-hoc but also invalid: Error: code-signature of app is invalid! FreeCol.app: a sealed resource is missing or invalid file modified: LICENSE file modified: ADDITIONAL_LICENSE_INFO file modified: ASSEMBLY_EXCEPTION file modified: LICENSE file modified: ADDITIONAL_LICENSE_INFO file modified: ASSEMBLY_EXCEPTION file modified: LICENSE file modified: ADDITIONAL_LICENS}

@stiangre i can confirm this is a valid build for Intel. i did have issues launching it due to the Ad-hoc signature. even the normal workaround "right click => open" did not work. however the build launched and worked fine after manually removing the quarantine from the command-line

FreeCol 1.2 cannot be launched on Intel Macs

i can confirm the problem still exists in the newest version. it claims to have the version "SNAPSHOT" instead of '1.5.3'

ah sorry, didn't remember filing this before

version numbers broken on macOS

yes, thanks for the confirmation ;) looking forward to a fixed version 1.5.1