sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radu Cotescu (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SLING-9379) Make the MetadataMojo look for scripts in the default locations
Date Thu, 16 Apr 2020 15:45:00 GMT

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

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

Implemented in [commit 3516ad1|https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/3516ad1].

> Make the MetadataMojo look for scripts in the default locations
> ---------------------------------------------------------------
>
>                 Key: SLING-9379
>                 URL: https://issues.apache.org/jira/browse/SLING-9379
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Bundle Maven Plugin 0.2.0
>
>
> The {{MetadataMojo}} uses the {{src/main/scripts}} folder as the default value for the
folder where it will scan for Sling scripts, however this is the default folder for scripts
that normally will be precompiled. It would be nice if the mojo would also try to scan {{src/main/resources/javax.script}},
in order to reduce the configuration a developer must provide for generating capabilities
for bundled scripts.
> In addition to that, the configuration should allow multiple source folders to be defined,
so that bundles can provide both precompiled scripts and bundled scripts at the same time.



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

Mime
View raw message