Actually, a symlink might even work better. If the app is then copied
to another machine, with a different flavor of the OS on it, the
symlink should still work OK. On the other hand, doing the copy would
allow me to update the timestamps as Mike Hall suggested.
One more thing to do would be to compile everything with Java 1.4.2,
instead of a newer version, so that the jar files will still work on
Panther systems.
Bill
> Bill Janssen wrote:
>
> >The app binary (CFBundleExecutable) is actually an executable bash
> >script that renames itself, then copies into its place a copy of
> >/System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/MacOS/JavaAppl
> >icationStub,
> >then exec's that copy of JavaApplicationStub.
>
> I recommend this shorter pathname:
>
> /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub
>
> You could also create a symlink instead of doing a copy. I have no reason
> to suspect a symlink won't work, though it hasn't been tried extensively.
>
> -- GG
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Java-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/java-dev/email@hidden
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
