[
https://issues.apache.org/jira/browse/GROOVY-11000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711733#comment-17711733
]
Paul King commented on GROOVY-11000:
------------------------------------
I imagine the issue you are facing is to do with the fact that {{groovy-json}}
is an OSGi fragment. But nothing has changed in regard to that for 2.5, 3.0 or
4+, so I am unsure where the problem might be. I tried putting together a
reproducer but it fails on all versions including 2.5.x. Since others seem to
have this working, I suspect I am probably too rusty with OSGi and am missing
some required piece of config. In my testing, I can install and activate
`groovy` and can install the `groovy-json` fragment but I receive a missing
requirement `groovy-json` when trying to access the `groovy.json` package from
another bundle. So, there is some issue with resolving `groovy-json`.
The issue wouldn't have been a problem with 2.4.x since that uses a groovy-all
jar not a groovy-all pom, so the fragment concept isn't needed for that. There
are some groovy modules which need to be fragments (due to classloader
requirements) but possibly not all need to be fragments. We'd need to have some
tests in place to convince ourselves that any changes we make in that regard
are correct.
So, long story short, I am unsure we need to make changes in Groovy, since
others seem to have it working. If we do need changes, they might be
non-trivial, so some assistance would be welcome in working out what needs to
change and/or testing said changes.
> Unable to load FastStringService in OSGI Environment in Groovy-all: 3.0.11
> version
> ----------------------------------------------------------------------------------
>
> Key: GROOVY-11000
> URL: https://issues.apache.org/jira/browse/GROOVY-11000
> Project: Groovy
> Issue Type: Bug
> Environment: Production
> Reporter: neha
> Priority: Major
> Fix For: 3.0.11
>
> Attachments: cpissue.groovy, groovyissue.PNG
>
>
> After upgrading to 3.0.11, getting attached error in OSGI environment while
> running a groovy script.
> Its seems same issue has been fixed in 4.0.9 groovy version.
> (https://issues.apache.org/jira/browse/GROOVY-10881)
> We are using grails and latest grails version also supports groovy - 3.0.11
> version. So, we can't upgrade groovy to latest version.
> We need a patch on top of 3.0.11 groovy version.
> Please provide
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
