[SLING-9161] The Scripting Bundle Maven Plugin should allow more flexible ways for the project structure

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting Bundle Maven Plugin 0.1.0
• Fix Version/s: Scripting Bundle Maven Plugin 0.2.0
• Component/s: Maven Plugins and Archetypes
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 27/Feb/20 11:48
• Updated: 22/Jun/20 13:18
• Resolved: 05/Mar/20 21:24

Description

The Scripting Bundle Maven Plugin currently imposes the following restriction for the project structure:

<scriptsDirectory>/<sling-resourceType>/<version>/[<METHOD>.]<name>[.<selector>][.<requestExtension>].<script-extension>

In this case the <sling-resourceType> will be limited to one folder, which means that resource type namespacing should be done similar to Java package names. While this is not wrong, the plugin should also allow defining the resource types using Sling's already established conventions [0], e.g. resource tree paths relative to a search path. In addition, the <version> folder should become optional.

[0] - https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#scripts-for-get-requests

Issue Links

• is a child of: SLING-9207 Unify the support for bundled scripts
• relates to: SLING-9181 The Scripting Bundle Tracker should be extended to allow more flexibility for resource type definitions
• links to: GitHub Pull Request #1