java.library.path fix for MacOS X (7145798)

Michael Hall mik3hall at
Sun Feb 19 10:50:06 PST 2012

On Feb 19, 2012, at 11:37 AM, Mike Swingler wrote:

> Sure. Anything except plain "Java" will work for that Info.plist key, technically. "JavaRuntime" is as specific as a descriptor as I've heard so far.

Well the two being in sync would be a technical concern in changing the value. Change the launch program and it'd be fine. What you call it isn't what doesn't work right now and I'm not so concerned with. Normally the app bundle is sort of opaque anyhow. As far as name goes I'd be fine with whatever. 
Having the test or demo application include something that exercises these things or even having separate JUnit or other tests that try all the plist key values would still seem to be a good idea to me. Greg indicated that he did some testing. If the SwingSet demo is it, it's a little sparse for exercising possible options. But, the plist included is absent almost any special handling. Greg, had posted a ant classpath tag to the system location for the SwingSet demo but I didn't see where even that is in the application. 
The XCode project doesn't hang for me which is much improved, but without some sort of effort my part still doesn't build. The errors seem like what I've seen related to the XCode and Java update out of sync but not positive. I can track that down when I have a chance. Otherwise I would of tracked down further where the two have interdependencies, which is the difficulty I reported, or at least strongly suspected.

More information about the macosx-port-dev mailing list