Bill Janssen wrote:
>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.
Correct. An absolute symlink will refer to whatever is at the absolute
indirect path.
>On the other hand, doing the copy would
>allow me to update the timestamps as Mike Hall suggested.
You can get an "update" by calling 'touch' on the app-bundle dir (the
.app). What Mike Hall was referring to, I think, was that LaunchServices
will not update its cache UNLESS and until the main app-bundle dir is
modified. That is, only changing things internally, such as the content of
Info.plist, won't change LS's caching.
That said, if you don't change Info.pllist, it shouldn't matter. So if
Info.plist still says "Foo" is the executable, and you rename the
shell-script "Foo" to "Bar", and put a symlink to JavaApplicationStub named
"Foo" in its place, then LS wouldn't know the difference. I think. But
just to be asfe, what the heck, add a 'touch' to the shell-script.
>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.
Yes. I always do this, or whatever the minimum JRE is, should it be less
than 1.4.
-- 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
