Re: Re: JDK used for compiling

>>> The default choice is the highest version of the default vm set for the
>>> arch.
>> Hmm. And the code is also compiled against the newest class library?
>>
>> For the given reasons (see the example code) that's not a good idea.
>> Code compiled with a too new JDK might actually throw
>> NoSuchMethodErrors, for example.
>>
> 
> People committing ebuilds and marking them stable should make sure that
> it works with the lowest atom specified by the dependencies.

This is an undoable task, for two reasons:

1) First, things can break, after recompiling with a newer JDK version.
So adding a new JDK to the tree, would yield a HUGE wave of testing.
2) Second, the Exceptions only get thrown at runtime - so especially, if
such an issue is conditional (inside an if-statements) it maybe never
discovered.


Of course, as said in the other postings, the code always compiles fine.
It just isn't sure to assume that it runs with JDK X when it is compiled
against JDK Y - especially if or although Y is newer than X.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHQfrg7Ww7FjRBE4ARAio0AKDTnPyfpC21ot1ZunhdWBhe0suYUwCg2s3t
5wNo3fCKCxFOqFLrrbbqeq0=
=x9ei
-----END PGP SIGNATURE-----