[cn4j-alliance] convergence of MicroProfile Context Propagation interfac

[Nathan Rauh <nathan.rauh@xxxxxxxxxx>]

I have been asked
to let the CN4J group know that with Jakarta EE 10, we will be proceeding
with our plan to contribute interfaces from MicroProfile Context Propagation
into Jakarta EE Concurrency by copying the method signatures to the respective
Jakarta EE Concurrency classes, according to the original plans outlined
on the MicroProfile Context Propagation github project home page, https://github.com/eclipse/microprofile-context-propagation
which states:

"It is intended
that ManagedExecutor methods will one day be added to ManagedExecutorService,
and for a single implementation to be capable of simultaneously implementing
both interfaces, both currently as well as after adoption into Jakarta
EE."

and 

"It is intended
that ThreadContext methods will one day be added to EE Concurrency’s ContextService
and for a single implementation to be capable of simultaneously implementing
both interfaces, both currently as well as after adoption into Jakarta
EE."

To achieve this,
I have opened the following issues, which are in the proposed release plan
for Jakarta EE Concurrency in Jakarta EE 10

Issue #40
Completion stages backed by ManagedExecutorService
https://github.com/eclipse-ee4j/concurrency-api/pull/104

Issue #100
ContextService methods for contextualizing individual dependent stage actions
https://github.com/eclipse-ee4j/concurrency-api/pull/138

Issue #101
Completion stages backed by a ContextService
https://github.com/eclipse-ee4j/concurrency-api/pull/139

These, as well
as a few other issues relating to MicroProfile, are labeled with microprofile
to identify
the relationship and for convenience.
It will ultimately
be up to the Jakarta EE Concurrency community as to whether they end up
including all, some, none, or various portions of these.