public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: Gentoo Java <gentoo-java@lists.gentoo.org>
Subject: [gentoo-java] RFC: JDK version handling in the future
Date: Sat, 10 Oct 2009 13:48:31 +0300	[thread overview]
Message-ID: <4AD0667F.8070600@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

             reply	other threads:[~2009-10-10 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 10:48 Petteri Räty [this message]
2009-10-10 19:04 ` [gentoo-java] RFC: JDK version handling in the future Alistair Bush

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AD0667F.8070600@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-java@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox