Date: Thu, 21 Feb 2008 13:03:33 +0100 From: Ulf Lilleengen <lulf@FreeBSD.org> To: glewis@FreeBSD.org Cc: java@FreeBSD.org Subject: [PATCH] Javavmwrapper defaulting to bsd.java.mk wrong? Message-ID: <20080221120333.GA36004@carrot.studby.ntnu.no>
next in thread | raw e-mail | index | archive | help
--9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. --=20 Ulf Lilleengen --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHvWiUCILg8nMIdCURAqdIAJ46a50kvWNLX5p1U3ho3pCcRJFzZQCfSsXa /0X8QJjoBrnzt9hEWlBBPuY= =KZLn -----END PGP SIGNATURE----- --9amGYk9869ThD9tj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080221120333.GA36004>