Vassal 3.2.2 on Mac OSX won't start

Hey Joel - I’m trying to set up my Mac for development and am hitting on this problem. I’ve ensured the vengine.jar comes first in the module dependencies. Any other ideas?

The installed version of VASSAL 3.2.13 runs fine outside of the development environment.

-David

2014-08-20 22:57:35,542 [0-main] INFO VASSAL.launch.StartUp - Starting 2014-08-20 22:57:35,560 [0-main] INFO VASSAL.launch.StartUp - OS Mac OS X 10.8.5 2014-08-20 22:57:35,560 [0-main] INFO VASSAL.launch.StartUp - Java version 1.6.0_65 2014-08-20 22:57:35,560 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.13 2014-08-20 22:57:35,560 [0-main] INFO VASSAL.launch.Launcher - Player 2014-08-20 22:57:37,110 [0-IconFactory-preload] INFO VASSAL.tools.icon.IconFactory - VASSAL images folder found at file:/Users/davidsullivan/IdeaProjects/vasl/target/classes/images/ 2014-08-20 22:57:37,121 [0-AWT-EventQueue-0] ERROR VASSAL.tools.ErrorDialog - java.lang.IllegalStateException: Icon Family VASSAL not found at VASSAL.tools.icon.IconFactory.getIcon(IconFactory.java:119) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.ServerAddressBook$AddressBookEntry.getIcon(ServerAddressBook.java:693) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.ServerAddressBook.getCurrentIcon(ServerAddressBook.java:432) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.AddressBookServerConfigurer.setValue(AddressBookServerConfigurer.java:99) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.AddressBookServerConfigurer$2.propertyChange(AddressBookServerConfigurer.java:77) ~[Vengine-3.2.13.jar:na] at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) ~[na:1.6.0_65] at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276) ~[na:1.6.0_65] at VASSAL.chat.ServerAddressBook.setCurrentServer(ServerAddressBook.java:385) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.ServerAddressBook.setCurrentServer(ServerAddressBook.java:345) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.AddressBookServerConfigurer.setValue(AddressBookServerConfigurer.java:95) ~[Vengine-3.2.13.jar:na] at VASSAL.chat.AddressBookServerConfigurer.<init>(AddressBookServerConfigurer.java:62) ~[Vengine-3.2.13.jar:na] at VASSAL.launch.BasicModule.initServer(BasicModule.java:192) ~[Vengine-3.2.13.jar:na] at VASSAL.launch.BasicModule.build(BasicModule.java:145) ~[Vengine-3.2.13.jar:na] at VASSAL.launch.BasicModule.build(BasicModule.java:111) ~[Vengine-3.2.13.jar:na] at VASSAL.build.GameModule.init(GameModule.java:855) ~[Vengine-3.2.13.jar:na] at VASSAL.launch.Player.launch(Player.java:83) ~[Vengine-3.2.13.jar:na] at VASSAL.launch.Launcher$1.run(Launcher.java:149) ~[Vengine-3.2.13.jar:na] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) ~[na:1.6.0_65] at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:715) ~[na:1.6.0_65] at java.awt.EventQueue.access$400(EventQueue.java:82) ~[na:1.6.0_65] at java.awt.EventQueue$2.run(EventQueue.java:676) ~[na:1.6.0_65] at java.awt.EventQueue$2.run(EventQueue.java:674) ~[na:1.6.0_65] at java.security.AccessController.doPrivileged(Native Method) ~[na:1.6.0_65] at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:86) ~[na:1.6.0_65] at java.awt.EventQueue.dispatchEvent(EventQueue.java:685) ~[na:1.6.0_65] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296) [na:1.6.0_65] at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211) [na:1.6.0_65] at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201) [na:1.6.0_65] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196) [na:1.6.0_65] at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188) [na:1.6.0_65] at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) [na:1.6.0_65]

Place the VASSAL jar ahead of the source code in the module dependencies fixed the problem. No idea why. :confused:

Thus spake djsullivan:

Place the VASSAL jar ahead of the source code in the module dependencies
fixed the problem. No idea why. :confused:

I suspect that has something to do with the paths of the icon files
being different if they’re in the JAR vs in the source tree.


J.