For each spec, the following updates need to happen, refer this doc for instructions:
[ ] 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.4 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}"' '{}' \;
For each spec, the following updates need to happen, refer this doc for instructions:
[ ] 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.4 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 tojakarta.*
:find . -type f -name '*.java' -exec sed -i '' s/javax./jakarta./ {} +
[ ] 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}"' '{}' \;
[ ] Perform step 4/5/6 in this doc
[ ] Perform a RC release off the branch
master