Hibernate projects should already have a Jandex if they need to, so we can safely ignore them.
This is especially important because Hibernate projects (e.g. Envers) may add new entity types to an application, which could lead Hibernate Search to perform Jandex index discovery for the corresponding jar (e.g. hibernate-envers.jar), which in some cases might fail because the JAR doesn’t contain a Jandex index and it cannot be built (e.g. because of Spring’s repackaged JARs that rely on nested JARs, which we cannot open because that requires {{java of [https://hibernate.nioatlassian.filenet/browse/HSEARCH-4744|https://hibernate.FileSystems#newFileSystem(javaatlassian.nio.file.Path, java.util.Map<java.lang.String,?>net/browse/HSEARCH-4744|smart-link])}} and Java 13). |
|