Paul Bakker

The current master contains instructions to generate OSGi metadata, but it is not correct yet. Fixed in this PR: https://github.com/goldmansachs/gs-collections/pull/17

It would btw be even better to combine API and impl in a single bundle, where only the API packages are exported. Currently it is necessary to export all implementation...

I agree, let's start with adding a module name, so that at least it becomes usable. Once we baseline on Spring Boot 3.0, which requires Java 17, it makes sense...

I'll have a look at the mechanism you linked to, that looks good. What are your general thoughts about features that are DGS specific and don't *need* to be in...

Yes, with https://github.com/apollographql/federation-jvm?tab=readme-ov-file#subscription-http-callback-support-for-spring-graphql On Mon, Apr 8, 2024 at 2:50 PM Greg Wardwell ***@***.***> wrote: > Does the release of DGS 8.5.0 > with > Spring GraphQL integration mean subscription...

As a side effect of some bigger news coming soon, this will actually be supported soon.

> Since object mappers in DGS framework rely on reflection, methods isSet() and setField() can stay private. I think this feature should really be usable stand-alone, without any framework changes....

Having the same issue. The fix by @julrich seems to fix the problem.

This is great! When is it going to be available? If we get this I can do a complete rewrite of the install part of containers for the Forge integration....

There is one more thing the Forge plugin would need. Some containers require configuration in arquillian.xml. I need to know what to put in there. Besides the required part it...