[
https://issues.apache.org/jira/browse/SLING-12437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933451#comment-17933451
]
Paul King edited comment on SLING-12437 at 3/21/25 10:03 AM:
-------------------------------------------------------------
I haven't checked what Sling uses yet but Apache Aries Spifly supported
services in fragments until 1.2.4. From 1.3.0, they turned them off:
https://github.com/apache/aries/commit/76f39f2#diff-aed8297fc5209027131b1f54544e00eb7614070832051a29561931ed6b933ab7
was (Author: paulk):
I haven't checked want Sling uses yet but Apache Aries Spifly supported
services in fragments until 1.2.4. From 1.3.0, they turned them off:
https://github.com/apache/aries/commit/76f39f2#diff-aed8297fc5209027131b1f54544e00eb7614070832051a29561931ed6b933ab7
> 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)
