This is somewhat complicated by the fact that on kfreebsd we still don't have
openjdk, so we're using GCJ/GIJ, which is really a 1.5 implementation.
If GCJ/GIJ can run 1.6 bytecode then absolutely this check should be 1.6 and
you can ignore the rest of this mail.
If it cannot, then it's more comp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Russ
On 17/05/12 21:07, Russ Allbery wrote:
>> To ensure that java libraries are compatible with all versions of
>> Java
>>> in the archive, it would be great to have a lintian check which
>>> warnings if the minimum bytecode version is exceeded
James Page writes:
> Its possible to get into the situation where bytecode is generated from
> source code that is not backwards compatible - javac by default will
> generate bytecode that is only forwards compatible.
> To ensure that java libraries are compatible with all versions of Java
> in
Package: lintian
Version: 2.5.7
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Currently Debian and Ubuntu ship three versions of Java - 5, 6 and 7.
Its possible to get into the situation where bytecode is generated from source
code that is not backwards compatible - javac by d
4 matches
Mail list logo
