You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2019/01/06 17:23:00 UTC

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

Romain Manni-Bucau created SLING-8198:
-----------------------------------------

             Summary: 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
            Reporter: Romain Manni-Bucau


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)