Thanks Malcolm,
Yes, a diff of Parser.jjt by itself will be fine. Not sure if that will
work though as it appears the line you edited in Parser.jjt is generated by
javacc.
WILL
----- Original Message -----
From: "Malcolm Edgar" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <velocity-dev@jakarta.apache.org>
Sent: Monday, September 19, 2005 10:41 PM
Subject: Re: [jira] Commented: (VELOCITY-373) Enhance ParseErrorException
Hi Will,
Ok I will get onto it. Is it alright for me to send you a diff of
Parser.jitthen. My understanding of the build process is:
Parser.jit -> Parser.jj -> Parser.java
I am looking forward to picking up a new Velocity 1.5 release.
regards Malcolm Edgar
On 9/20/05, Will Glass-Husain (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://issues.apache.org/jira/browse/VELOCITY-373?page=comments#action_12329949]
Will Glass-Husain commented on VELOCITY-373:
--------------------------------------------
Also, it's a little easier (though not required) if you include all the
files together in the diff. If you are using subversion, run diff on the
directory. If you are using an IDE, you might be able to use that to
generate the diff.
Thanks again for contributing.
> Enhance ParseErrorException
> ---------------------------
>
> Key: VELOCITY-373
> URL: http://issues.apache.org/jira/browse/VELOCITY-373
> Project: Velocity
> Type: Improvement
> Components: Source
> Versions: 1.5
> Environment: Operating System: other
> Platform: Other
> Reporter: Malcolm Edgar
> Priority: Minor
> Fix For: 1.5
> Attachments: ParseErrorException.txt, ParseErrorException.txt,
ParseException.txt, Parser.txt, Template.txt
>
> Enhance the ParseErrorException to report:
> * template name (path)
> * error line
> * error column
> The Click framework attempts to render the template error highlighting
the
> offending line. However when templates or macros are included in a page,
the
> source of the error cannot be determined from the ParseErrorException
message.
> If the additional properties could be added to the ParseErrorException
> the framework could accurately render the offending template error. This
> information should enable quicker debugging of usage errors by all
Velocity users.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
