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
Field/parameter "packageToScan" is now a String value, limiting packages to scan to one single package. As I do not want to scan the entire codebase, it would be convenient to be able to list multiple sub-packages to scan.
It seems like a quick fix in AbstractReflectionsComponentFinderStrategy
the includePackage method in the reflections API takes a vararg of Strings, making it possible to easily refactor ComponentFinder to accept a list/array of packages to scan.
Hi
Field/parameter "packageToScan" is now a String value, limiting packages to scan to one single package. As I do not want to scan the entire codebase, it would be convenient to be able to list multiple sub-packages to scan.
It seems like a quick fix in AbstractReflectionsComponentFinderStrategy
.filterInputsBy(new FilterBuilder().includePackage(componentFinder.getPackageToScan()))
the includePackage method in the reflections API takes a vararg of Strings, making it possible to easily refactor ComponentFinder to accept a list/array of packages to scan.
essentially changing this line to
.filterInputsBy(new FilterBuilder().includePackage(componentFinder.getPackagesToScan()))
that is, changing getPackageToScan to getPackagesToScan
This is also very relevant for multi-module builds.
E.g. when controllers depend upon services/repositories from other maven-modules.
The text was updated successfully, but these errors were encountered: