You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by vladbailescu <gi...@git.apache.org> on 2015/03/13 15:35:36 UTC
[GitHub] sling pull request: SLING-4499 - Sightly: Parsing errors should no...
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 <ba...@adobe.com>
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.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] sling pull request: SLING-4499 - Sightly: Parsing errors should no...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/sling/pull/71
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---