New rules are needed to migrate EAP 7 Application's maven projects (pom.xml), to use a dependency management compatible with EAP 8, due to the following changes on EAP BOMs:

• The “JBoss EAP Jakarta EE8” BOM was renamed to “JBoss EAP EE”, and its Maven Coordinates changed too, from org.jboss.bom:jboss-eap-jakartaee8 to org.jboss.bom:jboss-eap-ee
• The “JBoss EAP Jakarta EE8 With Tools” BOM was renamed to “JBoss EAP EE With Tools”, and its Maven Coordinates changed too, from org.jboss.bom:jboss-eap-jakartaee8-with-tools to org.jboss.bom:jboss-eap-ee-with-tools
• The “JBoss Jakarta EE8 APIs” BOMs are no longer distributed with JBoss EAP 8.0. The new "JBoss EAP EE" BOM should be used instead.
• The “JBoss EAP Runtime” BOM is no longer distributed with JBoss EAP 8.0. The new "JBoss EAP EE" BOM should be used instead.
• Several Jakarta EE and JBoss APIs artifacts, which were provided by the JBoss EAP BOMs, have changed Maven Coordinates, or were replaced by other artifacts:
  • com.sun.activation:jakarta.activation
  • org.jboss.spec.javax.annotation:jboss-annotations-api_1.3_spec
  • org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.0_spec
  • org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec
  • org.jboss.spec.javax.batch:jboss-batch-api_1.0_spec
  • org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec
  • org.jboss.spec.javax.el:jboss-el-api_3.0_spec
  • org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec
  • org.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec
  • org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec
  • org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec
  • com.sun.mail:jakarta.mail
  • org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec
  • org.jboss.spec.javax.servlet:jboss-servlet-api_4.0_spec
  • org.jboss.spec.javax.servlet.jsp:jboss-jsp-api_2.3_spec
  • org.apache.taglibs:taglibs-standard-spec
  • org.jboss.spec.javax.transaction:jboss-transaction-api_1.3_spec
  • org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.3_spec
  • org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec
  • javax.jws:jsr181-api
  • org.jboss.spec.javax.websocket:jboss-websocket-api_1.1_spec
  • org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.1_spec
  • org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.4_spec
  • org.hibernate:hibernate-core
  • org.hibernate:hibernate-jpamodelgen
  • org.jboss.narayana.xts:jbossxts

You may find the details about "when" to catch those issues, and how to "perform", at https://docs.google.com/document/d/1ipcBiA_tIvSTU-2IAAGSkCwgUf24SC_pRDMyjdBBlHQ/edit?usp=sharing

The ruleset implementation should be very similar to https://github.com/windup/windup-rulesets/blob/77b78950afd6a14cc0cb5ef0397e05158808701e/rules/rules-reviewed/eap7/eap72/maven-javax-to-jakarta.rhamt.xml (which handles artifacts first, and then boms)