Using Jakarta Data in a WildFly application requires the inclusion of Hibernate-generated classes in the deployment archive. Making this happen requires inclusion of the hibernate-jpamodelgen and hibernate-core artifacts in the application dependencies. (The latter is because the former generates classes that compile against core ORM types.)

To make this easy we should include hibernate-jpamodelgen in the 'with-tools' bom. This artifact is a build tool; it's not something the app compiles against, so it doesn't belong in the wildfly-ee-preview bom.

https://github.com/bstansberry/quickstart/tree/jakarta_data/todo-jakarta-data is an example of use. This bit we should eliminate:

https://github.com/bstansberry/quickstart/commit/4d74166a7bf404f1af655f0a7e406c596049fbfa#diff-e8df8c200160ff58a0aa7e8aac99ab2a673d8245d0293bbfdf54988316143621R125-R126

NOTE: I'm not proposing we include that Quickstart. At some point, probably for 35, we should have a Jakarta Data QS, but that may not be the right one. At this point it was just convenient to start with todo-backend as a base.