[
https://issues.apache.org/jira/browse/LOG4J2-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-1188:
--------------------------------
Description:
Plugin builders were introduced long ago as a way to configure plugin instances
while also maintaining a backward-compatible way to evolve the API of a plugin.
While this has been useful, there are other ways that would be nice to make a
plugin dependency injectable.
This should allow for an {{@Inject}} constructor to be used along with
supporting zero or more arguments in each {{@Inject}} method.
was:The use of the newBuilder() static method annotated with
{{@PluginBuilderFactory}}, while convenient, is unnecessary when constructing
plugins via configurations. This functionality should remain, but if a plugin
class has an inner class that implements {{Builder<T>}}, then that class can be
used without needing to specify it through another annotation.
> Allow plugins to be created through more flexible dependency injection
> patterns
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-1188
> URL: https://issues.apache.org/jira/browse/LOG4J2-1188
> Project: Log4j 2
> Issue Type: Improvement
> Components: Plugins
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Major
>
> Plugin builders were introduced long ago as a way to configure plugin
> instances while also maintaining a backward-compatible way to evolve the API
> of a plugin. While this has been useful, there are other ways that would be
> nice to make a plugin dependency injectable.
> This should allow for an {{@Inject}} constructor to be used along with
> supporting zero or more arguments in each {{@Inject}} method.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
