[
https://issues.apache.org/jira/browse/LOG4J2-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532880#comment-17532880
]
Volkan Yazici commented on LOG4J2-3497:
---------------------------------------
{quote}PluginManager's sole job is to keep track of Plugins by category. It
doesn't instantiate plugin instances so it has no knowledge of the data used in
a specific plugin reference.
{quote}
Okay, I see your point {{PluginManager}} is simply a registry of discovered
plugins. Any {{{}@Plugin-{}}}annotated class in the classpath is registered by
this class and it will do nothing else. Right? If so, 1) what is the difference
between {{PluginManager}} and {{PluginRegistry}} and 2) who is responsible for
performing {{ConstraintValidator}} checks?
> ConstraintValidator's are not employed by PluginManager
> -------------------------------------------------------
>
> Key: LOG4J2-3497
> URL: https://issues.apache.org/jira/browse/LOG4J2-3497
> Project: Log4j 2
> Issue Type: Bug
> Components: Plugins
> Reporter: Volkan Yazici
> Assignee: Matt Sicker
> Priority: Major
> Fix For: 2.18.0
>
>
> {{ConstraintValidator}}'s are not taken into account when plugins are
> collected via {{PluginManager}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
