There is a bug in the current software that prevents VASSAL from being run after it is compiled from the command-line. The fix is as follows:
/src/VASSAL/tools/icon/IconFactory.java
Replace the references to IMAGE_DIR in this file with ICON_DIR, most importantly in the function initVassalIconFamilys(). In its present state, VASSAL is searching for icons in the “images/” subfolder rather than in the “icons/” subfolder where they are located. A temporary workaround is to put the icons subfolder into a JAR: the software appears to find the icons by default when they are distributed as part of a jar.
Thus spake trevelyan:
There is a bug in the current software that prevents VASSAL from being
run after it is compiled from the command-line. The fix is as follows:
/src/VASSAL/tools/icon/IconFactory.java
Replace the references to IMAGE_DIR in this file with ICON_DIR, most
importantly in the function initVassalIconFamilys(). In its present
state, VASSAL is searching for icons in the “images/” subfolder rather
than in the “icons/” subfolder where they are located. A temporary
workaround is to put the icons subfolder into a JAR: the software
appears to find the icons by default when they are distributed as part
of a jar.
One of the purposes of the ‘make jar’ target in the Makefile is to ensure
that there’s a JAR from which to read icons. Use that.
I don’t want to add code solely for the case in which someone is running
VASSAL from a dev environment.
–
J.