[
https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967369#comment-14967369
]
Ralph Goers commented on LOG4J2-952:
Yes
> Add ConfigurationBuilder for progr
its code was merged into master?
> Add ConfigurationBuilder for programmatic configuration.
>
>
> Key: LOG4J2-952
> URL: https://issues.apache.org/jira/browse/LOG4J2-952
>
> been a while since I've worked on Log4j, this would be a good place for me
> to work again while I get familiar with the thousand new features. :)
>
> On 13 September 2015 at 14:36, Remko Popma wrote:
>
>> I'm done with the documentation changes for programmatic
s. As it's been a
> while since I've worked on Log4j, this would be a good place for me to work
> again while I get familiar with the thousand new features. :)
>
> On 13 September 2015 at 14:36, Remko Popma <mailto:[email protected]>> wrote:
> I'm done with
ures. :)
On 13 September 2015 at 14:36, Remko Popma wrote:
> I'm done with the documentation changes for programmatic configuration.
> Phew!
> I have nothing else in the pipeline for 2.4, and I also see no blockers in
> Jira.
>
>
> On Mon, Sep 14, 2015 at 3:57 AM, Remko Po
[
https://issues.apache.org/jira/browse/LOG4J2-952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-952:
Summary: Add ConfigurationBuilder for programmatic configuration. (was:
FAQ: How do I configure
I'm done with the documentation changes for programmatic configuration.
Phew!
I have nothing else in the pipeline for 2.4, and I also see no blockers in
Jira.
On Mon, Sep 14, 2015 at 3:57 AM, Remko Popma wrote:
> Almost done. I added a section on ConfigurationFactory. Will commit soon
4j 2. I propose we take a
>> stronger stance and remove the older example (the first one on the page)
>> that extends XmlConfiguration. This older example uses the builders and
>> factory methods to manually add Loggers/Appenders; I would like to
>> discourage direct use of
e.
Regards, and cya.
B.
On 09/13/2015 01:06 AM, Gary Gregory wrote:
So here we are WRT programmatic configuration, users' options are:
- The new builder API. Most flexible, not 100% type-safe, a typo in a
property name can mess you up.
- The sprinkling of Builder classes. Easy to code again
st one on the page)
>> that extends XmlConfiguration. This older example uses the builders and
>> factory methods to manually add Loggers/Appenders; I would like to
>> discourage direct use of the builders and factory methods.
>>
>> The only programmatic configuration u
stance and remove the older example (the first one on the page)
> that extends XmlConfiguration. This older example uses the builders and
> factory methods to manually add Loggers/Appenders; I would like to
> discourage direct use of the builders and factory methods.
>
> The only pr
the older example (the first one on the page) that
> extends XmlConfiguration. This older example uses the builders and factory
> methods to manually add Loggers/Appenders; I would like to discourage direct
> use of the builders and factory methods.
>
> The only programmatic
e a
> stronger stance and remove the older example (the first one on the page) that
> extends XmlConfiguration. This older example uses the builders and factory
> methods to manually add Loggers/Appenders; I would like to discourage direct
> use of the builders and factory methods.
nd
factory methods to manually add Loggers/Appenders; I would like to
discourage direct use of the builders and factory methods.
The only programmatic configuration use case that may not be solved (yet)
by the configuration builder API is the ability to modify the current
configuration (while the appl
e are WRT programmatic configuration, users' options are:
>
> - The new builder API. Most flexible, not 100% type-safe, a typo in a
> property name can mess you up.
> - The sprinkling of Builder classes. Easy to code against (fluent),
> type-safe, a bit brittle but less so than fa
So here we are WRT programmatic configuration, users' options are:
- The new builder API. Most flexible, not 100% type-safe, a typo in a
property name can mess you up.
- The sprinkling of Builder classes. Easy to code against (fluent),
type-safe, a bit brittle but less so than factory me
16 matches
Mail list logo
