Improve documentation for annotation filters with component scanning
Prior to this commit the documentation for annotation-based include and exclude filters used with component scanning did not explicitly mention the fact that annotations are considered a match if they are either present or meta-present on candidate classes. This commit improves the documentation in this regard. See gh-22551
This commit is contained in:
@@ -515,7 +515,7 @@
|
||||
<xsd:documentation><![CDATA[
|
||||
Controls the type of filtering to apply to the expression.
|
||||
|
||||
"annotation" indicates an annotation to be present at the type level in target components;
|
||||
"annotation" indicates an annotation to be present or meta-present at the type level in target components;
|
||||
"assignable" indicates a class (or interface) that the target components are assignable to (extend/implement);
|
||||
"aspectj" indicates an AspectJ type pattern expression to be matched by the target components;
|
||||
"regex" indicates a regex pattern to be matched by the target components' class names;
|
||||
|
||||
Reference in New Issue
Block a user