You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2015/03/16 11:13:38 UTC
[jira] [Resolved] (SLING-4499) Sightly: Parsing errors should not
show up in console/stdout
[ https://issues.apache.org/jira/browse/SLING-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu resolved SLING-4499.
---------------------------------
Resolution: Fixed
Fixed in [r1666945|https://svn.apache.org/viewvc?view=revision&revision=1666945].
> 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
> Assignee: Radu Cotescu
> 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)