>>> I might keep in mind there is still… >>> https://bitbucket.org/infinitekind/appbundler >> >> If it's truly a fork of AppBundler then it doesn't use it. AppBundler has >> it's own launcher code, the executable it produces is also called >> JavaAppLauncher (and may have been based on this). The Java class uses a >> different package, so it doesn't rely on JavaAppLauncher in rt.jar. >> >> I've yet to find any actual uses of JavaAppLauncher... it was part of the >> initial port but the native portion is not built (except for the native >> methods in apple.launcher.JavaAppLauncher which is in osxlib.dylib). None of >> it has been touched since then except to change copyright dates. > > As I remember there was an early port version of JavaAppLauncher that was > supported by Mike Swingler. I may have a copy pulled of that somewhere. Then > there was the Scott Kovatch and Greg Brown AppBundler project which came out > with an Oracle sponsored version of JavaAppLauncher. The infinitekind project > was forked off of that. If you are referring to the first pass Mike Swingler > supported code I would say there is probably no use of that by anyone at this > point, except maybe the copy I pulled which I'm not even using. Mike Swingler > could probably tell you more.
I asked Mike offline before polling the list, whatever's in the JDK source is unused by anything on the Oracle side. I think it's just carry over from the JarBundler app that Apple had for Java 6 that we never implemented. -DrD-
