That would require class path scanning.
Wouldn't it require scanning just for entities? I'd take it for granted that anything not being @Entity is going to be ignored by Hibernate. In the context of Hibernate Search I think we should be consistent with the "Hibernate way".
Also should we allow implementation details / complexity to break user expectations of a natural behaviour?
I am concerned about adding ORM specific behaviors to hibernate search. What should happen for other event generators?
Would you be OK in not having subclasses be considered in the Infinispan and non Hibernate ORM case (ad-hoc or alternative sources)?
I guess I could live with an option like SearchConfiguration#considerSubclassesAsIndexed().