From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MwZV8-0006mJ-98 for garchives@archives.gentoo.org; Sat, 10 Oct 2009 10:48:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 24043E0832; Sat, 10 Oct 2009 10:48:37 +0000 (UTC) Received: from petteriraty.eu (host.petteriraty.eu [188.40.80.83]) by pigeon.gentoo.org (Postfix) with ESMTP id 59A29E0832 for ; Sat, 10 Oct 2009 10:48:36 +0000 (UTC) Received: from [82.130.46.226] (qob2.kyla.fi [82.130.46.226]) by petteriraty.eu (Postfix) with ESMTPSA id 54A9029573 for ; Sat, 10 Oct 2009 10:48:35 +0000 (UTC) Message-ID: <4AD0667F.8070600@gentoo.org> Date: Sat, 10 Oct 2009 13:48:31 +0300 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1.23) Gecko/20090916 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-java@lists.gentoo.org MIME-Version: 1.0 To: Gentoo Java Subject: [gentoo-java] RFC: JDK version handling in the future X-Enigmail-Version: 0.96.0 OpenPGP: url=http://users.tkk.fi/~praty/public.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig666EA3314BA2A8D964D4F2EA" X-Archives-Salt: a9bb22e1-8a7e-4ee6-9e0b-608c2ef64124 X-Archives-Hash: a3b4b52908bfe015e8cd86c61b60af6f This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig666EA3314BA2A8D964D4F2EA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Inspired by the recent ruby version handling post on gentoo-dev I came up with this scheme to handle JDK versions in the future: 1. Have a JAVA_VERSION USE_EXPAND variable containing: "java5 java6" or any JDK versions supported at that time. 2. The minimum flag that is on is used for the JDK version to emerge things. Just setting -source is not in reality making things run with the target, it just makes the bytecode usable for older JDKs. 3. When depending on something java the eclasses will automatically pull in libraries targeting the right JDK using EAPI 2 use dependencies. Benefits: - You can compile everything to the highest byte code available - Simpler maintenance and marginally faster emerges when build.xml files don't always need to be rewritten. - Solve bug 161622 (java-config should look into the deptree when deciding wich vm to use) If this seem sane, it's best to rewrite the eclasses at the same time to delete all the cruft that we have collected over time like the different rewriter implementations. Regards, Petteri --------------enig666EA3314BA2A8D964D4F2EA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrQZoIACgkQcxLzpIGCsLT8NwCeJwe7InEt3VX1iG7e4kMBXKvU UkkAnjQXSp6C5aW3Zvm/kmG+G/nV3ohG =P2bh -----END PGP SIGNATURE----- --------------enig666EA3314BA2A8D964D4F2EA--