My application is not correct. It only runs on the build system.
Anyhow: You can still use the Routeconverter.icns
Some observations: did you see the forum thread at sourceforge about the eventpump (first 2 posts)?
Also: you (and some others too) specify the "-XstartOnFirstThread". However, java on OSX is Quartz based, not X11 based. Next to that are the (Snow)Leopard Xwindows versions on OSX also Quartz based and no longer on the "old fashioned" X11 basis. X11 applications use the functions in the Xwindows/client system, which are Quartz on OSX.
It means that java applications on OSX do not need to call X11 (as first thread) at all, but display directly via Quartz.
Most probably that's the reason why attempts to use "java -XstartOnFirstThread -jar Routeconverter.jar" result in a hanging application: X11 is simply not started by OSXes java.
(I started X11 in advance as well and then used the same command, but that also resulted in a hanging app).
Anyhow: You can still use the Routeconverter.icns
Some observations: did you see the forum thread at sourceforge about the eventpump (first 2 posts)?
Also: you (and some others too) specify the "-XstartOnFirstThread". However, java on OSX is Quartz based, not X11 based. Next to that are the (Snow)Leopard Xwindows versions on OSX also Quartz based and no longer on the "old fashioned" X11 basis. X11 applications use the functions in the Xwindows/client system, which are Quartz on OSX.
It means that java applications on OSX do not need to call X11 (as first thread) at all, but display directly via Quartz.
Most probably that's the reason why attempts to use "java -XstartOnFirstThread -jar Routeconverter.jar" result in a hanging application: X11 is simply not started by OSXes java.
(I started X11 in advance as well and then used the same command, but that also resulted in a hanging app).