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

["Radu Cotescu (Jira)" <ji...@apache.org>]

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

Radu Cotescu resolved SLING-9161.
---------------------------------
    Resolution: Fixed

Fixed in [commit d50e074|https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/d50e0742d6a20d6126e0687c90233cf1395a1287].

> The Scripting Bundle Maven Plugin should allow more flexible ways for the project structure
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-9161
>                 URL: https://issues.apache.org/jira/browse/SLING-9161
>             Project: Sling
>          Issue Type: Improvement
>          Components: Tooling
>    Affects Versions: Scripting Bundle Maven Plugin 0.1.0
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Bundle Maven Plugin 0.2.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Scripting Bundle Maven Plugin currently imposes the following restriction for the project structure:
> {noformat}
> <scriptsDirectory>/<sling-resourceType>/<version>/[<METHOD>.]<name>[.<selector>][.<requestExtension>].<script-extension>
> {noformat}
> 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



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