Page History
...
- Use Resources API
- Split scripts vs. classes (scripts stay in current workspace and functionality for executing scripts stay stays in groovy the Groovy module. Support for classes will be removed from Groovy module and placed in resources workspace)
- Maintain support for scripts in JCR > scripts
...
- module-names may contain dashes but Java does not allow having a package name with dashes. Scripts (which are eventually compiled as Java classes) need to declare a valid, unique package to compile and for this whole feature to work.
- if module name is in the package name dash ( - ) needs to be replaced (by underscore? or use some other convention)
- next to the templates (convenient to edit, but hard to specify correct package name) vs. special folder (would make it easier to have package name w/o module name in it
- ideally would favor no special tricks
...
As far as I could see, having a special folder in the light module structure, e.g. one called groovy, would not solve the issue because
...
Overview
Content Tools