You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org> on 2007/03/08 01:04:40 UTC
[jira] Closed: (VELOCITY-373) Enhance ParseErrorException
[ https://issues.apache.org/jira/browse/VELOCITY-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Schmiedehausen closed VELOCITY-373.
-------------------------------------------
> Enhance ParseErrorException
> ---------------------------
>
> Key: VELOCITY-373
> URL: https://issues.apache.org/jira/browse/VELOCITY-373
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects 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.jjt.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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org