Scan for specific classes rather than just packages with classpath scanning

Hi,

I would like to request for @EntityScan to be able to provide the ability to scan for specific entities class, rather than based on package. E.g @EntityScan(classes={"com.aa.ClassA", "com.aa.ClassB")) will only scan for these 2 classes and other classes in the same package will NOT be scan.
Searching internet shows many people asking for such capabilities and end up having to write some codes to circumvent this. Adding such capabilities made life easy for developers

Likewise, should also provide similar way to configure this in properties/yaml as well. E.g spring.jpa.entity-scan-classes=com.aa.ClassA,com.aa.ClassB

[sbrannen]

In fact, I was also suggesting to be able to exclude scan for specific classess e.g @EntityScan(excludeClasses = "MyClass1"), so that all classes are scanned except for the listed ones.

I’m not convinced that selecting individual entity classes (instead of scanning the package) is worthwhile, but I can foresee it being useful to be able to exclude particular classes based on a filter. That’s also what @wilkinsona suggested in https://github.com/spring-projects/spring-boot/issues/29193#issuecomment-1005667589.

Note that @ComponentScan already supports excludeFilters.

[hannah23280]

In fact, I was also suggesting to be able to exclude scan for specific classess e.g @EntityScan(excludeClasses = "MyClass1"), so that all classes are scanned except for the listed ones.

I’m not convinced that selecting individual entity classes (instead of scanning the package) is worthwhile, but I can foresee it being useful to be able to exclude particular classes based on a filter. That’s also what @wilkinsona suggested in spring-projects/spring-boot#29193 (comment).

Note that @ComponentScan already supports excludeFilters.

Even though i support the idea of exclude on filter, but why not make it more complete by also giving the ability to include only specific ones. To cater for a wide range of developers.