[
https://issues.apache.org/jira/browse/SLING-12437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933244#comment-17933244
]
Paul King commented on SLING-12437:
-----------------------------------
I had some interesting observations. For Groovy 4.0.26, we changed Groovy
modules to fragments since this is what some folks using Eclipse PDE seemed to
think they needed. It means that you can now include groovy-macro:4.0.26 with
sling and the tests now pass. But being a fragment, it is only resolved not
started, so other modules which seem to need to be started for sling no longer
work. We have some more thinking to do.
> 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)
