[
https://issues.apache.org/jira/browse/SLING-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990603#comment-13990603
]
Carsten Ziegeler commented on SLING-3546:
-----------------------------------------
Yes, but why is this tested at all? It is based on internals of the jsp
scripting and how the generated code looks like. We didn't replace jasper, the
exception is still there - we just moved the compiler out of the bundle and use
a compiler from another bundle
> SLING2617Test fails, JasperException not found
> -----------------------------------------------
>
> Key: SLING-3546
> URL: https://issues.apache.org/jira/browse/SLING-3546
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Reporter: Bertrand Delacretaz
> Assignee: Carsten Ziegeler
> Fix For: Launchpad Testing 7
>
>
> The SLING2617Test (from launchpad/integration-tests) fails, probably due to
> the recent JSP compiler changes, due to not finding the
> org.apache.sling.scripting.jsp.jasper.JasperException class.
> The failing script is bean-set-get.jsp [1].
> {code}
> An error occurred at line: 23 in the jsp file: /apps/nt/unstructured/html.jsp
> The type org.apache.sling.scripting.jsp.jasper.JasperException cannot be
> resolved. It is indirectly referenced from required .class files
> ...
> An error occurred at line: 25 in the jsp file: /apps/nt/unstructured/html.jsp
> org.apache.sling.scripting.jsp.jasper.JasperException cannot be resolved to a
> type
> {code}
> [1]
> https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2617/bean-set-get.jsp
--
This message was sent by Atlassian JIRA
(v6.2#6252)
