You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/05/05 18:24:20 UTC

[jira] [Commented] (SLING-3546) SLING2617Test fails, JasperException not found

    [ https://issues.apache.org/jira/browse/SLING-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989670#comment-13989670 ] 

Carsten Ziegeler commented on SLING-3546:
-----------------------------------------

I think this test is wrong, org.apache.sling.scripting.jsp.jasper. has never been exported and the test is relying on internals of the jsp compilation.
I've no clue what the test is actually testing though....

>  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
>             Fix For: Scripting JSP 2.0.30
>
>
> 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)