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 2013/12/14 04:57:09 UTC
[jira] [Closed] (SLING-2730) Allow JSPs to be excluded from
compilation in maven-jspc-plugin
[ https://issues.apache.org/jira/browse/SLING-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2730.
-----------------------------------
> Allow JSPs to be excluded from compilation in maven-jspc-plugin
> ---------------------------------------------------------------
>
> Key: SLING-2730
> URL: https://issues.apache.org/jira/browse/SLING-2730
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Affects Versions: Maven JSPC Plugin 2.0.6
> Reporter: Ben Peter
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Maven JSPC Plugin 2.0.8
>
> Attachments: SLING-2730-take2.patch, SLING-2730.patch
>
>
> JSPs may contain symbols that are declared not in the JSP itself, but in a JSP that includes it (although that may be considered bad style).
> including.jsp:
> <%String foo = "bar"; %>
> <%@include file="included.jsp" %>
> included.jsp:
> <%= foo %>
> The result is that such a JSP does not compile on its own and the goal will fail.
> This can be circumvented if individual JSPs can be excluded from compilation.
> Excluding them from the resources to start with does not help, as they are still required for the including JSPs to compile.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)