/cc @DavideD (hibernate-reactive), @gavinking (hibernate-reactive), @gsmet (hibernate-orm,jakarta)

related to #35603

I suspect the annotation processor won't work great in dev mode, at least in Gradle -- I think @FroMage made it work with Maven, at least.

I also added support for Gradle a while ago so we're good :)

We will need to think about dependency management for Jakarta Data as well.

So honestly this is a bit of a Shit User Story:

Hibernate Data Repositories 6.6 works in Quarkus. Just add:

• jakarta.data:jakarta.data-api and
• org.hibernate.orm:hibernate-jpamodelgen

as dependencies via Maven.

As of Jakarta Persistence 3.2, Hibernate Processor is an integral part of the programming model, but even for earlier versions it's annoying to have it not be there by default.

And the Jakarta Data API is tiny, I really see no particularly good reason to not just include it in the Hibernate ORM extension.

WDYT @yrodiere @maxandersen @FroMage ?

As for JD, sure.

But hibernate-jpamodelgen has to be added as an APT processor to the compiler options. Not as a "regular" dependency.

We do have an issue open to investigate making this automatic, but it requires support from tooling.

Without this, is there any way to not have to manually change my Maven pom to select the correct version of Hibernate Processor every time I update Quarkus?

Without this, is there any way to not have to manually change my Maven pom to select the correct version of Hibernate Processor every time I update Quarkus?

Yes. Since a few versions, the Maven Compiler plugin is taking the version from the dependency management if available: https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#annotationProcessorPaths (see the comment in the example).

It can also apply the dependency management to the dependencies of the annotation processor (see option below).

Oh, OK, thanks, that's not so bad then.

Tried it; it worked.

@gsmet It's Maven only, I suppose? Anything similar for Gradle?

I have no idea how Gradle handles it and if they do. All I could find that could apply was https://stackoverflow.com/a/70397869/5043585 so it might be supported with the extra config.

In the Maven world, they introduced this feature fairly recently.

OK.

As of Jakarta Persistence 3.2, Hibernate Processor is an integral part of the programming model, but even for earlier versions it's annoying to have it not be there by default.

Agreed it's annoying, but as explained above, doing otherwise would require much more control over app developers' tooling than we currently have.

Adding the processor to the BOM will have to do.

And the Jakarta Data API is tiny, I really see no particularly good reason to not just include it in the Hibernate ORM extension.

WDYT @yrodiere @maxandersen @FroMage ?

I wonder why it's not a dependency of hibernate-core itself, if that's the case.

I agree it should be part of our BOM at least. As to adding it as a dependency of quarkus-hibernate-orm... I'd personally prefer handling that through Panache 2's dependencies, but in the end I guess I'm +0.