[
https://issues.apache.org/jira/browse/SLING-9068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17550853#comment-17550853
]
Bertrand Delacretaz commented on SLING-9068:
--------------------------------------------
As per
https://stackoverflow.com/questions/1564448/format-parseexception-with-javacc
it looks like we'll need to store a (partial) copy of the input, probably by
wrapping the input Reader, to be able to recreate the context based on the
positional information provided by the {{currentToken}} when an Exception is
thrown.
> Add more context to ParseException
> ----------------------------------
>
> Key: SLING-9068
> URL: https://issues.apache.org/jira/browse/SLING-9068
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Affects Versions: Repoinit Parser 1.6.2
> Reporter: Angela Schreiber
> Priority: Minor
>
> today the repo init grammar doesn't come with dedicated exception handing and
> thus the parser will fail with messages that can make it hard to spot actual
> problem... specially in a lengthy repo-init as it is present with Adobe AEM.
> Example:
> {code}
> org.apache.sling.repoinit.parser.impl.ParseException: Encountered " "," ", ""
> at line 115, column 46.
> Was expecting:
> ")" ...
>
> at
> org.apache.sling.repoinit.parser.impl.RepoInitParserImpl.generateParseException(RepoInitParserImpl.java:3095)
> [org.apache.sling.repoinit.parser:1.3.2]
> {code}
> if i am not mistaken this should be doable be adding explicit exceptions to
> the grammar.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
