Werner Keil

It may be good to refresh the local SNAPSHOT but you should not need to build it yourself, because [indriya 285](https://app.circleci.com/pipelines/github/unitsofmeasurement/indriya/285/workflows/ba6c051b-4b1f-4935-ab09-10e98442a510/jobs/2072) deployed the latest snapshot on the Sonatype Snapshot repo....

Thanks, is there a scenario to replicate that, e.g. in an app server or other cases with multiple class loaders?

This is a similar situation as #203. While it seems fine for JNoSQL to use a MicroProfile library in an implementation, it is not acceptable for the Spec/API (Jakarta NoSQL)

@otaviojava/all, please don't forget, that the final NoSQL release won't even be relevant to the Jakarta EE platform before Jakarta EE 10, so it is more than reasonable to consider...

@Emily-Jiang @otaviojava Note, that Jakarta EE has stronger compatibility requirements, therefore a frequently changing API is no good. Let's wait till MicroProfile becomes more mature and especially for the API...

I think I would rather stick to something like https://github.com/reactive-streams/reactive-streams-jvm. "For this reason, the same interfaces provided by https://www.reactive-streams.org in the org.reactivestreams package are used instead." so MP Reactive does...

But what does that mean for the PR, would it work now or only after adopting Java 11?

@waynebeaton Sorry to bother, but curious, are implementations supposed to use the Spec as a "Parent POM" like JNoSQL does here, or more like e.g. Krazo: https://github.com/eclipse-ee4j/krazo/blob/master/pom.xml which defines a...

Aside from the question of a parent POM, @waynebeaton wouldn't it make sense to also have this repository (and all other "jnosql-*" ones that are not archived) in https://github.com/eclipse-ee4j/ ?...

That's fine, not sure, if we could use the ``` org.eclipse.ee4j project 1.0.1 ``` like e.g. Tyrus or other implementations do already, regardless of the TLD? Otherwise I would rather...