Hi Paul, Thanks for the suggestion. Unfortunately, downgrading to Spifly 1.2.4 isn't a quick solution for me at the moment, as I'm currently using Spifly 1.3.7 and the ASM libraries are incompatible.
For now, I've a workaround by creating a Groovy fat JAR that includes the service loaders and repacks the dgminfo and all Require and Provide capabilities within the JAR and Export packages of all the Groovy stuff including the jarjar classes. Best regards, Matthias On Tue, 4 Mar 2025 at 13:55, Paul King <[email protected]> wrote: > > Hi Matthias, does using Groovy 4.0.26 with spifly 1.2.4 work as another > workaround for you? > > Cheers, Paul. > > On 2025/02/14 11:14:31 Matthias Leinweber wrote: > > Hi karafers, > > > > Following my investigation into the Groovy and OSGi issue, it appears > that > > Groovy is currently incompatible with OSGi. The developers plan to > > reintroduce fragment host functionality in a future release. > > > > In the meantime, the current workaround is to create a fat JAR that > > includes the necessary META-INF files. > > > > Just wanted to keep everyone informed. > > > > On Sat, 8 Feb 2025 at 16:36, Matthias Leinweber < > [email protected]> > > wrote: > > > > > Hi together, > > > > > > I am using groovy alot and just updated to karaf.4.7.7 camel 4.9.1 and > > > groovy 4.0.22. > > > > > > Somehow the dateutils overload for the date class seems not to work. In > > > groovy 3.0.9 the bundle was a fragment host. Do I need to do something > > > extra? > > > > > > Br Matthias > > > > > >
