See https://discourse.hibernate.org/t/hibernate-search-6-2-not-able-to-open-nested-jars/7979

This slipped through the cracks, and I think it has the potential of impacting many users (basically anyone using Spring + nested JARs). I think we should try implementing it right now, by changing the behavior of Hibernate Search when we detect JDK 13+, and perhaps providing a better exception message when on JDK 13+. Currently the exception message is Cannot open a ZIP filesystem for code source at '%1$s', because the URI points to content inside a nested JAR. A better alternative would be Cannot open a ZIP filesystem for code source at '%1$s', because the URI points to content inside a nested JAR. Run your application on JDK13+ to get nested JAR support, or disable JAR scanning by setting a mapping configurer that calls .discoverAnnotatedTypesFromRootMappingAnnotations(false)

Probably something we should backport to 6.2.