[ http://issues.apache.org/jira/browse/DERBY-73?page=comments#action_12367617 ]
Andrew McIntyre commented on DERBY-73: -------------------------------------- JavaCC 3.2 has an issue with lookahead that causes a failure in the test lang/db2compatibility.sql. However, I have tried the recently released JavaCC 4.0, and it fixes that issue and all tests passed cleanly, so at some point we will likely upgrade to that version. > 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 > > 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: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
