Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 04 Sep 2008 18:02:23 +0530
From: Mayuresh Nirhali <Mayuresh.Nirhali@Sun.COM>
Subject: Re: New version of JavaCC
In-reply-to: <48BD369F.6010809@sun.com>
Sender: Mayuresh.Nirhali@Sun.COM
To: derby-dev@db.apache.org
Message-id: <48BFD557.30901@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <48BD2583.5040400@Sun.com> <48BD369F.6010809@sun.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070423)

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 
>>
>>
>>
>