Hibernate ORM 5.5 is out and it supports Jakarta EE through separate artifacts, which have been transformed to use the Jakarta EE API instead of the Java EE API (they are almost identical, except they exist in different packages).

We should do the same for Hibernate Search:

• Create new "-jakarta" variants (a new module) for artifacts that rely on Jakarta EE instead of Java EE. These modules will simply take the code of the original artifact and replace Java EE dependency with a Jakarta EE dependency through bytecode transformation.

• Create test modules for these modules. Ideally we should just transform existing tests and avoid copy/pasting them.

I believe this mainly affects the ORM mapper and the JSR-352 integration, but any module relying on a Java EE spec might need its own "variation" to support Jakarta EE.

There are examples of how to do the transformation in Hibernate ORM, but unfortunately it's using Gradle plugins. We will have to find out how to do this with Maven.