[
https://issues.apache.org/jira/browse/SLING-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217674#comment-14217674
]
ASF GitHub Bot commented on SLING-4175:
---------------------------------------
GitHub user santiagozky opened a pull request:
https://github.com/apache/sling/pull/45
SLING-4175
Would this patch be acceptable to fix
https://issues.apache.org/jira/browse/SLING-4175 ?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/santiagozky/sling SLING-4175
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/45.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 #45
----
commit 62cef3a235c1ee7921f91650e25709125d4e6140
Author: Santiago Garcia Pimentel <santiago@santiago-2.local>
Date: 2014-11-19T09:59:16Z
SLING-4175
----
> Sightly: Do not catch exceptions in ResourceRuntimeExtension and
> IncludeRuntimeExtension
> ----------------------------------------------------------------------------------------
>
> Key: SLING-4175
> URL: https://issues.apache.org/jira/browse/SLING-4175
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Konrad Windszus
> Labels: Sightly
>
> Currently all exceptions being thrown during the execution of
> data-sly-include and data-sly-resource are caught and only logged.
> Instead those exceptions should be just wrapped (to ease debugging during
> development) and also to be consistent with {{sling:call}} (SLING-3459).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
