db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-73) Ability to compile under JDK1.5
Date Fri, 24 Feb 2006 01:44:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-73?page=all ]

Andrew McIntyre updated DERBY-73:

    Attachment: javacc40.diff

Patch with necessary changes for building with JavaCC 4.0. OPTIMIZE_TOKEN_MANAGER is no longer
a supported option, and the generated code for mtGrammar includes a catch block for RuntimeException
which uses a new method in RuntimeException introduced in JDK 1.4, so it became necessary
to move the compilation of mtGrammar.java into the impl_tools_jdk14 target.

> Ability to compile under JDK1.5
> -------------------------------
>          Key: DERBY-73
>          URL: http://issues.apache.org/jira/browse/DERBY-73
>      Project: Derby
>         Type: Improvement
>   Components: Build tools
>     Reporter: Jeremy Boynes
>  Attachments: derby_jdk15_build.patch, derby_jdk15_build2.patch, javacc40.diff
> Compilation fails when using JDK1.5 due to
> 1) no specification of language level
> 2) use of "enum" as identifier
> The language issue results in the use of the new StringBuilder class for string concatenation
resulting in code that will not run on earlier JVMs.
> Dropping the langauge level will allow it to compile but warnings are generated due to
the use of "enum" as an identifier; with 1.5 this becomes a reserved word

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message