Dirk Fauth

> I have tried to use the extension once or twice and failed to make it work. I'm not sure if there is an issue with the extension itself or...

@nikhilnanivadekar That makes it easy to solve the build issues. :) I removed `p2-feature` and `p2-repository` from the `modules`, so the p2 update site is not built anymore as part...

@nikhilnanivadekar With my PR merged, the build of the Eclipse Collections p2 update site is separated from the main build. That means - first build and publish the Eclipse Collections...

@motlin > What's the difference between then? Does ServiceProvider also power the generation of manifest entries? Yes, that is actually the main reason for using that annotation. > Actually looking...

> What about the annotation? Is it possible to avoid it? Even compile-time-retention annotation dependencies show up as dependencies when searching sites like mvnrepository.com. We'd prefer to show up as...

@donraab Yes this PR helps address both 2 and 3. Yes I added 6.4.0 because 7.0.0 needs Java 17 for the execution. You can also build using Java 17 and...

There was a similar discussion here. https://github.com/eclipse/microprofile-config/issues/716 Different topic for different annotations, but maybe the provided scope could work for you.

I added the provided scope and did some further tests. I noticed that without the `@aQute.bnd.annotation.spi.ServiceConsumer` in the API, the JPMS resolution will fail, because the `uses` statements for the...

I have already provided a PR for this issue. Not sure what you want to do now.

Further investigation results: I added the following blocks to the reflect-config.json to make some things work: ``` { "name" : "java.lang.Exception", "allDeclaredConstructors" : true, "allPublicConstructors" : true, "allDeclaredMethods" : true,...