RouteConverter and Mac OS X

[hvdwolf]

That assumption is not valid for my release process. The prereleases are always the latest versions you can get. And I update them at least once a week.

Well, the release version mentions 1.33 where as the Prerelease mentions 1.31.3 with a new version 1.32 available. That's confusing and that's why I assumed that the prelease versions were older.

I'm using the Maven osxappbundle-maven-plugin and thought it would produce reasonable bundles... Any hints regarding the pom.xml are appreciated.

I did have a look at it but it's really java related and really complicated and it seems that it packages all dependent jars as such in the bundle whereas your complete jar already contains all these dependendency jars ("jar tf jarfile" is one of the few commands I know). That's also why the java -jar Routeconverter.jar works (apart from the map): it contains everything and is completely portable.

From which in conclude that this does not start the Java 6 but the Java 5?

The java preferences tool on OSX mentions an immediate switch. To be sure I rebooted and the message is no longer displayed. I assume the java tool does switch it but maybe there were some java-5 left-overs in memory.
Just to report as complete as possible see the startup messages from a "clean" java-6 start:

Code:

java -jar RouteConverter.jar
java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at slash.navigation.gui.Application.invokeNativeInterfaceMethod(Application.java:85)
    at slash.navigation.gui.Application.openNativeInterface(Application.java:94)
    at slash.navigation.gui.Application.launch(Application.java:103)
    at slash.navigation.converter.gui.RouteConverter6.main(RouteConverter6.java:48)
Caused by: java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)
    at org.eclipse.swt.internal.C.<clinit>(Unknown Source)
    at org.eclipse.swt.widgets.Display.<clinit>(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:169)
    at org.eclipse.swt.graphics.Device.<clinit>(Unknown Source)
    at chrriis.dj.nativeswing.swtimpl.NativeInterface$InProcess.initialize(NativeInterface.java:425)
    at chrriis.dj.nativeswing.swtimpl.NativeInterface$InProcess.access$0(NativeInterface.java:424)
    at chrriis.dj.nativeswing.swtimpl.NativeInterface.initialize(NativeInterface.java:221)
    at chrriis.dj.nativeswing.swtimpl.NativeInterface.open(NativeInterface.java:239)
    ... 8 more
java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at slash.navigation.gui.Application.invokeNativeInterfaceMethod(Application.java:85)
    at slash.navigation.gui.Application.runNativeInterfaceEventPump(Application.java:98)
    at slash.navigation.gui.Application.launch(Application.java:123)
    at slash.navigation.converter.gui.RouteConverter6.main(RouteConverter6.java:48)
Caused by: java.lang.IllegalStateException: Cannot run the event pump when the interface is not initialized!
    at chrriis.dj.nativeswing.swtimpl.NativeInterface.runEventPump(NativeInterface.java:378)
    ... 8 more
Logging to /var/folders/+R/+RmeG2o8EleS+UbdOPEbWE+++TI/-Tmp-/RouteConverter.log

It starts with an error "Can't open <blah blah> due to unknow file type" (note:translated back to english from dutch) for the source. This is due to the fact that the application somehow tries to open a folder instead of a file.

Some users reported this to me and I'm confused... do you have an idea what can cause this error?

On OSX the file handle can be: "file", "folder", "file+folder". I assume the third is used but I don't know java. Only AppleScript and some basic C.

This is the real issue - can you manage to use the 32-bit Java 6 version? Or is it easier if I'd package a RouteConverter with an 64-bit SWT-library?

The non-standard java-6 for Leopard only comes as a 64bit version. A 64bit RouteConverter.jar with a 64bit swt would be very nice. I'm verry happy to test it.

My java-5 system version is a universal "ppc7400/i386/x86_64".
Maybe you already know about the "Universal" concept. In that case you can skip the following <Universal>section, otherwise please read it.
<Universal>
Mac comes from ppc hardware and switched early 2006 to intel. For this they "invented" the universal concept. Every binary and library is built for the specific hardware and then "lipo merged". Tiger was ppc/i386. Leopard is mostly ppc/i386/x86_64, partly ppc/i386 and in some libraries/binaries/frameworks "ppc/i386/ppc64/x86_64". SnowLeopard abandoned the ppc platform and is "i386/x86_64". On snowLeopard you have the option (for Universal apps) to right-click the app->Get Info and set it to "automatic", "always run as 32bit", "always run as 64bit". Java can be set via the Java tool in the Utilities folder in the Applications folder.
</Universal>

The bundle principle: The bundle is actually nothing more then a special folder structure and due to some special files the OS and file manager (Finder) recognises it as an App and displays it as a single file. The bundle principle has the advantage that you can stuff everything in it that is not standardly supported on the OS or the OS version. It might be possible to pack the entire java 1.6 inside the bundle. This will blow up the bundle from the current 6 MB to 135MB and maybe more when more dependencies need to be bundled. I don't like that approach, but did have a look at it using the soylatte BSD ported 32bit java6 version. That one is based on OpenMotif which makes the gui look terribly ugly and doesn't make the app work better. It makes it even worse. The map is not displayed either.

Do you have more options for me to test?

The ones above? Would be great!

I did them all I think. More options? (a 64bit swt perhaps? )