You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/03/18 14:54:00 UTC

[jira] [Created] (SLING-9217) The JSPC Maven plugin should allow configuring the package name under which JSPs are compiled

Radu Cotescu created SLING-9217:
-----------------------------------

             Summary: The JSPC Maven plugin should allow configuring the package name under which JSPs are compiled
                 Key: SLING-9217
                 URL: https://issues.apache.org/jira/browse/SLING-9217
             Project: Sling
          Issue Type: Improvement
          Components: Maven Plugins and Archetypes
            Reporter: Radu Cotescu
            Assignee: Radu Cotescu
             Fix For: JSPC Maven Plugin 2.2.0


The JSPC Maven plugin currently uses the default package of the JSP compiler for prefixing the package names under which JSPs are precompiled. However, for projects that want to provide the precompiled JSPs in bundles and use them in conjunction with the Apache Sling Scripting Bundle Tracker, the package name identifies the resource type. Therefore the JSPC Maven plugin should allow to set the {{org.apache.sling.scripting.jsp.jasper.Constants.JSP_PACKAGE_NAME}} system property and by default it should set it to the empty string.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)