Opened 2 years ago

Closed 2 weeks ago

#447 closed defect (fixed)

manual: Compile to Java 5 Bytecode

Reported by: Rurban Owned by: Evenson Not Org
Priority: major Milestone: 1.6.1
Component: other Version: 1.5.0
Keywords: docs Cc:
Parent Tickets:


Since rc0 to 1.5.0 you removed one part of the outdated compile to Java 5 Bytecode,
but one headline still is "Compile to Java 5 Bytecode". It's now 6-8.

Please change to "Compile to Java Bytecode"


Change History (4)

comment:1 Changed 2 years ago by Evenson Not Org

The default target for the compilation is indeed Java 6 (see <>), but we haven't implemented the Java 6 verification scheme introduced in bytecode 50.x. So, we are in a weird state where our compiler indeed emits "50.0" as the class format, but with the old ("original") bytecode verification present.

I need to investigate this a bit, but will change the headline in the User Manual to something more accurate when I decide what that statement should be.

Last edited 2 years ago by Evenson Not Org (previous) (diff)

comment:2 Changed 2 years ago by Evenson Not Org

Milestone: 1.6.0
Owner: set to Evenson Not Org
Status: newassigned
Version: 1.5.0

comment:3 Changed 2 weeks ago by Evenson Not Org


Ticket retargeted after milestone closed

comment:4 Changed 2 weeks ago by Evenson Not Org

Resolution: fixed
Status: assignedclosed


Our compiler emits version 49.0 bytecode, corresponding to the Java 5 Standard Edition.

When we compile our Java source, the code emitted depends on what we set the javac target version to currently "1.6" by default corresponding to version 50.x bytecode of the Java 6 Standard Edition.

We have noted this in the manual as well as <> hopefully clearing up this confusion.

Note: See TracTickets for help on using tickets.