[PATCH] Javavmwrapper defaulting to bsd.java.mk wrong?

[Ulf Lilleengen]

Hello,

As I was trying to use jdk16 and diablo-jdk15 on the same machine, it would
always default to jdk15. I figured the javavmwrapper script tries to use the
bsd.java.mk PREFERRED_VERSION to determine this. This lead me to question if
there is any good reason that bsd.java.mk should be checked before the
versions set in javavms?

Attached is a patch which adds "support" for Java 1.6 to the wrapper script,
but also changes the order in how the java version to be used is. I'm no big
user of java, so I'm not sure if there is a reason for the old behaviour, so
excuse me if this is wrong.

-- 
Ulf Lilleengen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-java/attachments/20080221/bbc96c15/attachment.pgp