This gets even worse if Jakarta NoSQL was supposed to join the platform in say Jakarta EE 10, 11 or similar.
At least one compatible implementation must be available for that, so JNoSQL cannot wait for MP 5 or 6 including the correct MP Config, it needs a Jakarta EE 10 or 11 compatible MP Config and an implementation (like Smallrye) before that.
This is the same for any compatible Jakarta EE implementation, if MP specs like Config are not capable of that advanced availability, then they are unacceptable for Jakarta EE even to implementations.
Werner
Gesendet von Mail für Windows 10
Hello,
This cannot block or stiffle us for too Long. If MP-Config won’t find a solution for that (and it has to also due to some of the stuff being discussed in the new CN4J list https://www.eclipse.org/lists/cn4j-alliance/msg00001.html) we have to replace it with something else, there are so many other proper config Frameworks out there e.g. Apache Commons Config and it wouln’t be the first Apache Project used by JNoSQL.
Werner
Hello everyone, I few updates about this topic:
There is a proposal from Red hat about the CN4J alliance and how both Jakarta and Eclipse MicroProfile will work together, please, join the email list and also the proposal:
Hello everyone,
First I wish everybody happy holidays.
We're in the processing of upgrading the project to use Jakarta EE 9 as a minimum requirement.
I already created the Jakarta NoSQL spec API with this PR:
https://github.com/eclipse-ee4j/nosql/pull/55
Michael Redlich has volunteered to modernize the JNoSQL repository: https://github.com/eclipse/jnosql
That is an excellent opportunity to help the project.
--
--
