Jakarta EE 9.1 Alignment

[Emily-Jiang]

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

[njr-11]

It needs to be considered that javax replacement with jakarta is not always correct. Doing a global replace is fine to start out with, but both the developer submitting the pull and the reviewer need to manually inspect every spot that is replaced to account for javax packages that should not be converted, such as javax.naming, javax.sql, and so forth. A compilation attempt cannot be counted upon to detect mistakes because many of the occurrences will be in documentation and code examples rather than compiled classes.