[
https://issues.apache.org/jira/browse/LOG4J2-860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945487#comment-16945487
]
ASF subversion and git services commented on LOG4J2-860:
--------------------------------------------------------
Commit ff7ab765c9f45167e5b12cae9a367464402aa210 in logging-log4j2's branch
refs/heads/master from Matt Sicker
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=ff7ab76 ]
Update docs for LOG4J2-860
Signed-off-by: Matt Sicker <[email protected]>
> Unify plugin builders and plugin factories
> ------------------------------------------
>
> Key: LOG4J2-860
> URL: https://issues.apache.org/jira/browse/LOG4J2-860
> Project: Log4j 2
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 2.2
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Major
> Fix For: 3.0.0
>
>
> Before we can even settle on a preferred way to create plugins reflectively,
> it would be nice to combine the PluginAttribute and PluginBuilderAttribute
> annotations. In fact, allowing for flexibility in dependency injection for
> creating plugins would be better than strictly allowing factory methods or
> builder classes only. For instance, setter methods could be annotated for
> injection which allows for further customization.
> Since the ability to reflect on a parameter to get its name wasn't added
> until Java 1.8 (and alternatives require using bytecode libraries like asm),
> it would be nice to add some sort of plugin validation to the annotation
> processor to prevent users from forgetting to specify an attribute name when
> attached to a parameter instead of a field.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
