[SLING-3546] SLING2617Test fails, JasperException not found

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Launchpad Testing 10
• Component/s: Scripting
• Assignee: Carsten Ziegeler
• Reporter: Bertrand Delacretaz
• Created: 05/May/14 14:15
• Updated: 06/May/14 13:12
• Resolved: 06/May/14 05:39

Description

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].

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

[1] https://svn.apache.org/repos/asf/sling/trunk/launchpad/integration-tests/src/main/resources/integration-test/issues/sling2617/bean-set-get.jsp

Issue Links

• relates to: SLING-3545 SlingJSPTaglibTest fails due to missing ELContextWrapper/JspValueExpression