hg: macosx-port/macosx-port/jdk: Initial cut of a the .jre/.jdk loading JavaAppLauncher template.

[Michael Hall]

> 
> This check-in provides a JavaAppLauncher project that creates a shell .app bundle, copies in a 1.7.0.jre (or optionally, 1.7.0.jdk) into it's Contents/PlugIns directory, and uses the Info.plist to initialize the JVM and call into a launcher which invokes the app's specified main().
> 
> Right now, this launcher and project file only exist in the source, and don't produce any artifacts in the build output.
> 
> What we are looking for now are some ideas how to provide this technology in an easy to use format for the app developers in the OpenJDK community. How would you like make/use/invoke/build this stuff into/around your own apps? Should we build an .app shell as part of the jdk build output? Is the project file on it's own sufficient? Should there be a build.xml in the .jdk bundle that your IDE should invoke with the Info.plist details passed as parameters? Let us know what works best for you!

Sorry, still lagging on some of this stuff.

So there is no universal build executable you could construct your own application bundle out of, along the lines of a drop in JavaApplicationStub replacement? That might be good for now.

How about a JarBundler type application to construct a application bundle from a gui'd interface?

What version of XCode is actually required to open the project?