You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/05/04 09:23:00 UTC

[jira] [Resolved] (SLING-3103) Groovy extemsions for dealing with JCR and Spock

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

Carsten Ziegeler resolved SLING-3103.
-------------------------------------
    Resolution: Won't Fix

> Groovy extemsions for dealing with JCR and Spock
> ------------------------------------------------
>
>                 Key: SLING-3103
>                 URL: https://issues.apache.org/jira/browse/SLING-3103
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Victor Saar
>            Priority: Major
>         Attachments: SLING-3103.patch, sling-groovy-extensions.pdf
>
>
> A while ago I wrote a set of Groovy extensions aimed at making it easier to work with JCR. The main use case for this is probably testing and it includes an extension for the Spock testing framework, as well. But it could certainly be used for non-testing code.
> I think that Sling would be a good place for these extensions to live in. They are not particularly tied to Sling, but could be further extended to the Resource API for example.
> I'll attach a patch and some documentation so that people can get an idea of what's covered. (The patch currently adds a separate groovy artifact in contrib/extensions/groovy, because I didn't know where to put it else. I just realized that there is a Groovy extension bundle already, so it could certainly be added there.)
> I'm looking forward to feedback.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)