A followup of WFLY-12490 , many javax artifacts are being replaced by jakarta ones, and a new section should be added to Migration Guide to alert users about the issue, and how to solve it.

The following artifact replacements should be applied by users in their Maven projects, otherwise build and/or testing will fail:

• com.sun.mail:javax.mail -> com.sun.mail:jakarta.mail
• javax.activation:activation -> com.sun.activation:jakarta.activation
• javax.enterprise:cdi-api -> jakarta.enterprise:jakarta.enterprise.cdi-api
• javax.inject:javax.inject -> jakarta.inject:jakarta.inject-api
• javax.json:javax.json-api -> jakarta.json:jakarta.json-api
• javax.json.bind:javax.json.bind-api -> jakarta.json.bind:jakarta.json.bind-api
• javax.persistence:javax.persistence-api -> jakarta.persistence:jakarta.persistence-api
• javax.security.enterprise:javax.security.enterprise-api -> jakarta.security.enterprise:jakarta.security.enterprise-api
• javax.validation:validation-api -> jakarta.validation:jakarta.validation-api
• org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec -> org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.4_spec
• org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec -> org.jboss.spec.javax.transaction:jboss-transaction-api_1.3_spec