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/02/27 11:49:00 UTC

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

Radu Cotescu created SLING-9161:
-----------------------------------

             Summary: 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
             Fix For: Scripting Bundle Maven Plugin 0.2.0


The Scripting Bundle Maven Plugin currently imposes the following restriction for the project structure:
{noformat}
<scriptsDirectory>/<sling-resourceType>/<version>/[<METHOD>.]<name>[.<selector>][.<extension>].<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, e.g. resource tree paths relative to a search path. In addition, the {{<version>}} folder should become optional.



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