[ 
https://issues.apache.org/jira/browse/SLING-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360419#comment-14360419
 ] 

ASF GitHub Bot commented on SLING-4499:
---------------------------------------

GitHub user vladbailescu opened a pull request:

    https://github.com/apache/sling/pull/71

    SLING-4499 - Sightly: Parsing errors should not show up in console/stdout

    * Added custom error listener to the Lexer as well, as per Sam Harwell's 
suggestion: http://stackoverflow.com/a/18137301/831507
    * Updated the error listener to also accept Lexer recognizers.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vladbailescu/sling 
SLING-4499_sightly_parsing_errors

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/71.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #71
    
----
commit 93636dbd58935c903920e5e18876bf61184ce8a6
Author: vladbailescu <[email protected]>
Date:   2015-03-13T14:34:16Z

    SLING-4499 - Sightly: Parsing errors should not show up in console/stdout
    
    Added custom error listener to the Lexer as well, as per Sam Harwell's 
suggestion: http://stackoverflow.com/a/18137301/831507
    Updated the error listener to also accept Lexer recognizers.

----


> Sightly: Parsing errors should not show up in console/stdout
> ------------------------------------------------------------
>
>                 Key: SLING-4499
>                 URL: https://issues.apache.org/jira/browse/SLING-4499
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Sightly Engine 1.0.0
>            Reporter: Vlad Bailescu
>            Priority: Trivial
>             Fix For: Scripting Sightly Engine 1.0.0
>
>
> At the moment if Sightly encounters a parsing error (for input like 
> {{$\{a-b\}}}) it will output a line in the console/{{stdout}}: {{line 1:4 
> token recognition error at: '-'}}
> This should not happen



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to