MP 5.0 Jakarta EE 9.1 alignment

MP 5.0 will be the Jakarta EE 9.1 alignment without any other functional update from each MicroProfile Component specification. MP 5.0 will include the following MicroProfile component specifications:

• Config
• Fault Tolerance
• Metrics
• Health
• Open Tracing
• Open API
• JWT
• Rest Client

For each spec, the following updates need to happen, refer this doc for instructions:

• Create a branch called jakarta91-branch off master to perform Jakarta EE 9.1 alignment

• Only jakarta namespace changes are allowed in the release without any other functional changes with the exception of typos or tck fixes

• pom.xml: utilise microprofile-parent 2.1 as it has pulled in all of the Jakarta EE 9.1 as well as the necessary TCK dependencies (see this PR on how to)

• spec docs: rename Java EE to Jakarta EE, rename javax to jakarta: find . -type f -name '*.asciidoc' -exec sed -i '' s/javax./jakarta./ {} +

• Update all javax to jakarta for all java files import javax.* needs to be updated to jakarta.*: find . -type f -name '*.java' -exec sed -i '' s/javax./jakarta./ {} +

• • TCKs
• • APIs

• Update bnd file: find . -type f -name ‘*.bnd' -exec sed -i '' s/javax./jakarta./ {} +

• service loader file javax.* to jakarta.*: find . -type f -name "javax*" -exec sh -c 'mv "$0" "${0/javax/jakarta}"' '{}' \;

• deliver the changes to both jakarta91-branch and master

• Perform a RC release off the branch jakarta91-branch

[majidmostafavi]

Hello Emily I want to help with this issue. Please tell me what should I do.

[Emily-Jiang]

I created a new release for MP Fault Tolerance 4.0-RC5, which pulls in a small link update in the spec to point to the jakarta spec. @ederks85 please feel free to pull in the new update. Since the change does not affect api etc, it might not be necessary to do another release. just fyi