[
https://issues.apache.org/jira/browse/SLING-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742084#comment-16742084
]
Robert Munteanu commented on SLING-8198:
----------------------------------------
[~romain.manni-bucau] - it would be great for our tooling to be reusable
because the more eyes there are on the better :-) I'm not sure if anyone has
any short-term plans to work on this, but if you can submit a pull request I'd
be more than happy to review and apply it.
> Add an option to jspc-maven-plugin to drop sling dependency
> -----------------------------------------------------------
>
> Key: SLING-8198
> URL: https://issues.apache.org/jira/browse/SLING-8198
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Affects Versions: Maven JSPC Plugin 2.1.0
> Reporter: Romain Manni-Bucau
> Priority: Major
>
> Hi guys,
> would be very nice to be able to generate JSP without any dependency on a
> particular runtime (tomcat, sling etc).
> Having a portable=true|false flag in the plugin which would, when set to
> true, avoid all org.apache.sling. usages would be awesome.
> Concretely, replacing HttpJspBase is quite trivial - methods can be generated
> in the jsp directly without any issue. Dropping
> org.apache.sling.scripting.jsp.jasper.runtime.AnnotationProcessor is
> generally possible - it is not needed for all JSP. Note that the same applies
> to _el_expressionfactory which can be looked up lazily.
> Not sure it is a goal for sling but there is no jsp compiler out there usable
> to deploy the jsp in any servlet/jsp container, can be very valuable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
