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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JSPC Maven Plugin 2.2.0
• Component/s: Maven Plugins and Archetypes
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 18/Mar/20 14:53
• Updated: 22/Jun/20 13:13
• Resolved: 20/Mar/20 13:56

Description

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.

Issue Links

• is a child of: SLING-9207 Unify the support for bundled scripts
• is blocked by: SLING-9228 Export the name of the System property which is used by the Jasper compiler to set the default package name for generated classes