[
https://issues.apache.org/jira/browse/SLING-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583143#comment-13583143
]
Carsten Ziegeler commented on SLING-2730:
-----------------------------------------
what do you think about supporting include, exclude patterns, like below? This
would be a little bit more to type if you want to exclude single jsps which
don't follow a pattern, but as soon as you have a pattern, you can just use it
- and this is more inline with other plugins and their configurations.
/**
* @parameter default-value="**"
*/
private String[] includes;
/**
* @parameter
*/
private String[] excludes;
> 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
> Attachments: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
