[jira] [Updated] (SLING-8198) Add an option to jspc-maven-plugin to drop sling dependency

["Konrad Windszus (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated SLING-8198:
-----------------------------------
    Affects Version/s: Maven JSPC Plugin 2.1.0
          Component/s: Maven Plugins and Archetypes

> 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)