[
https://issues.apache.org/jira/browse/SLING-12437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937594#comment-17937594
]
Roy Teeuwen commented on SLING-12437:
-------------------------------------
[~paulk] sling itself doesn't impose that you use spifly, it's a modular
framework where you can decide which dependencies you want. If you use the
sling starter, a reference application, then it contains following dependencies
to make groovy work, but they can be updated at any moment, there is no
dependency on a specific spifly version:
[https://github.com/apache/sling-org-apache-sling-starter/blob/master/src/main/features/groovy.json]
> Groovy macro library does not work properly in OSGi
> ---------------------------------------------------
>
> Key: SLING-12437
> URL: https://issues.apache.org/jira/browse/SLING-12437
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Reporter: Roy Teeuwen
> Assignee: Roy Teeuwen
> Priority: Major
> Fix For: Starter 13
>
>
> In the sling-starter project, all groovy dependencies are listed. One of them
> is groovy-macro, which does not properly work in an OSGi environment (or at
> least not in the current setup of the Sling 13 SNAPSHOT). It deletes all
> DefaultGroovyMethod methods from any POJO / POGO and adds the
> MacroGroovyMethod instead.
> My proposal is to delete the groovy-macro as library from the starter, I
> expect that [~dklco] just added all libraries that he saw were available at
> the time of adding the groovy feature file. If no one objects, I will do the
> change
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
