Hello,
Yes, I think we should upgrade to latest JavaCC and also backout/undo
the workaround.
Please let me know If I should reopen and create a patch for taking out
the workaround ?
Rgds
Mayuresh
Rick Hillegas wrote:
Hi Kristian,
Upgrading to the latest JavaCC on the 10.5 trunk sounds like a good
idea to me.
Regards,
-Rick
Kristian Waagan wrote:
Hello,
A new version of JavaCC has been released. 4.1 is a maintenance release.
We might want to upgrade or at least test with it, since the
community reported a bug against JavaCC.
The bug Derby was hit by:
https://javacc.dev.java.net/issues/show_bug.cgi?id=152
Relevant Derby Jira issue:
https://issues.apache.org/jira/browse/DERBY-2103
List of JavaCC fixes:
https://javacc.dev.java.net/issues/buglist.cgi?component=javacc&field0-0-0=target_milestone&type0-0-0=equals&value0-0-0=4.1
