Background
There has been a recent update on the Jakarta EE rights to Java trademarks. It is worth a read in detail since there will be a future impact on the Eclipse MicroProfile specifications. To be brief, Jakarta EE specifications can use the existing Java EE-related apis defined under the javax namespace, but will not be able to evolve the javax namespace. That means no additions, deletions, or modifications of existing javax APIs. The Jakarta EE community has an active discussion (thread title: “Transitioning Jakarta EE to the jakarta namespace”) discussing how to address the transition from the javax namespace to a jakarta namespace.
Current MicroProfile Status
MicroProfile is proceeding with its MicroProfile 3.0 release this month (June 11th, 2019) that utilizes Java EE 8 specification names and will use the javax namespace, including CDI, JAX-RS, JSON-P, JSON-B, and Common Annotations.
The MicroProfile community does not have a defined position on how to proceed with the namespace transition, and is awaiting a formal Jakarta EE community decision. However, many MicroProfile community members are also Jakarta EE community members and have been voicing their thoughts either on the aforementioned discussion thread or via various social media outlets in the context of the broader Jakarta EE community discussion.
Future MicroProfile Plans
The MicroProfile Community is awaiting a final Jakarta EE namespace decision, at which time it will begin the discussion on how to proceed. Jakarta EE 8 plans to continue using the javax.* namespace and, thus, will have no immediate impact on MicroProfile. The earliest potential impact to MicroProfile will likely be Jakarta EE 9, pending the final outcome of the namespace discussion. Stay tuned.
