You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -41,9 +42,12 @@ The annotation processor has to be added to the build, e.g. for Maven:
41
42
</plugin>
42
43
----
43
44
44
-
<1> Provide the fully qualified class name of the annotation processor that generates the metamodel.
45
-
<2> Add the `org.hibernate.search:hibernate-search-processor` dependency to the annotation processor path (a superset of the compile path), so the Java compiler can find the processor.
46
-
<3> Add the backend dependency, in this example, the <<backend-lucene,Lucene backend>>, to the annotation processor path.
45
+
<1> This setting is required for the annotation processor dependencies to be managed by the dependency management section.
46
+
Particularly useful when using <<compatibility-search-dependencies-bom,Hibernate Search BOM>>.
47
+
More information is available in https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#annotationProcessorPathsUseDepMgmt[Maven compiler plugin documentation].
48
+
<2> Provide the fully qualified class name of the annotation processor that generates the metamodel.
49
+
<3> Add the `org.hibernate.search:hibernate-search-processor` dependency to the annotation processor path (a superset of the compile path), so the Java compiler can find the processor.
50
+
<4> Add the backend dependency, in this example, the <<backend-lucene,Lucene backend>>, to the annotation processor path.
47
51
It is important to include the same backend that the application is using to make sure that the generated metamodel classes reflect all the backend specifics.
48
52
For example, backends might have different defaults, resulting in a different set of <<mapping-inspect-traits,search traits>> per specific field, depending on the backend.
0 commit comments