To be clear, this is to address a short-coming in Maven in terms of how it handles annotation processors that simply is not an issue in Gradle (which has first-class support for javac’s processorpath).

Starting in 6.3, hibernate-jpamodelgen defines some implementation dependencies.

When integrated TheRightWay into Gradle, users have no problem -

You can do “the same” in Maven albeit in a way fulgier syntax and without the ability to apply a platform (BOM) -

Unfortunately, what is easier in Maven is TheWrongWay, simply adding jpamodelgen as a normal compile or provided scope dependency. In either case, jpamodelgen’s implementation (runtime) scoped dependencies won’t be transitively added to the project’s compile classpath for the annotation processor to have access to them.

There is a large debate as to why this is wrong. Bottom line is that it can lead to leaking unwanted dependencies onto the project’s compile classpth.

To help here, we could consider making those dependencies api which translates to Maven’s compile scope which would then be transitively added to the project’s compile classpath.