SDK and JRE bundles

[Henri Gomez]

> I made a mistake in the symlink generation for the bundle's primary
> executable "libjli.dylib". The Mac OS X JVM detection system sniffs the
> primary executable of the bundle for architectures so it knows which modes
> the particular JVM bundle supports. Since the symlink was broken, there were
> no architectures to sniff, ergo, not really a JVM there.
> This has been fixed
> in: <http://hg.openjdk.java.net/macosx-port/macosx-port/jdk/rev/1b3e924c6db1>
> Also, the .jre bundle is not a valid JDK to install in JavaVirtualMachines
> (because it's not a JDK). It's really only interesting to developers who
> want to get started on bundling it in their apps - but we aren't done
> developing this yet.

Fix detected and allready rebuilding it.

.jre bundle is to be 'embedded' in apps, so it make sense to install
it elsewhere.
I was wondering if it won't be better to provide it as simple tarball file.

Advices welcomed