Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application does not start

on 02-11-29 7:00, Martin Warnett <email@hidden> wrote:

> Was the application installed at the same location? I have had a couple
> of reports on my application. It runs if installed in /Applications, but
> not if it is installed elsewhere. On most systems it runs regardless of
> where it was installed.

I haven't seen this myself, but we got reports from some customers that
claim this for our app. Under which circumstances can this happen? Does
anyone know? Is this something we can handle or work around in our App, or
is this something Apple would have to fix?

then Greg Guerin <email@hidden> wrote:

> When was the app-bundle created? With what tool? Under which version of
> Java? How did you compare files, the 'cmp' command?

The bundle and its JavaApplicationStub was somewhat oldish (created under
MacOS X 10.1, whith whatever Java tools were in vouge at that time). So,
yes, the JavaApplicationStub was not the latest variant. I've updated that
since. However, that wasn't the cause for my initial problem (but could
possibly be related to the failure to launch outside the Application folder,
mentioned above).

> Anyway, each version of Java on Mac OS X has had a different launcher-stub.
> In my experience, these stubs work fairly well across different OS
> versions, but maybe there's a problem with one particular combination of
> launcher-stub and OS version.
>
> Another possibility is that somehow the bundled launcher-stub has gotten
> corrupted. If this happens on one copy of the program but not another, you
> can have mysterious "unlaunchable" apps, whose misbehavior depends on their
> origin (fruit of a poison tree or not).

Yes, that's what I thought, since bringing a new JavaApplicationStub over
into the bundle (from another computer with a known working bundle for the
same version of our app). I then thought JavaApplicationStub simply got
corrupted. But when I then compared the contents of the working and non
working JavaApplicationStub (using good-ol Resorcerer), they were both the
same. So I figured it was some OS/Finder flags, or whatever. This was also
somewhat corroborated by the fact that using a newer version of StuffIt to
compress the same set of files made them travel and run safely.

> Finally, if you're still using the "MRJApp.properties" file, consider
> translating its declarations to the equivalent Info.plist form. The
> MRJApp.properties technique may have a subtle problem that only shows up on
> some 10.2 systems.

Yes, I'm still using the "MRJApp.properties" file. Didn't even know that had
changed. Does someone know a good place where the process of converting it
to Info.plist form is described? I assume it's a similar list of
property/value pairs, so the translation should be fairly mechanical.
Perhaps there's even some tool to do the conversion?

Mike
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Be sure to read the FAQ http://developer.apple.com/java/faq/ before posting
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.