Hi Matt,
On Tue, 21 Nov 2023 at 23:22, Matt Sicker wrote:
>
> This sounds like it might be a good basis for figuring out a parallel v3 API
> for a “hard to mis-use” style API. However, once you go that route, you start
> to wonder how useful templated log messages are when you can capture a
I agree with everything Remko said plus these extra comments.
Throwing is a convenience method to standardize the output when an application
will be throwing an exception. That, of course, means it isn’t a required
method. I doubt it is used very much. Of course, catching is its companion but
> On Nov 23, 2023, at 18:31, Piotr P. Karwasz wrote:
>
> Hi Matt,
>
>> On Tue, 21 Nov 2023 at 23:22, Matt Sicker wrote:
>>
>> This sounds like it might be a good basis for figuring out a parallel v3 API
>> for a “hard to mis-use” style API. However, once you go that route, you
>> start
github-actions[bot] closed pull request #5: Bump
org.springframework:spring-framework-bom from 6.1.0 to 6.1.1
URL: https://github.com/apache/logging-log4j-jakarta/pull/5
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
github-actions[bot] commented on PR #5:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/5#issuecomment-1824937518
Changes are applied by CI in 14a91d49c6fe432e9df0e0b8429d01dbf036bf13
--
This is an automated message from the Apache Git Service.
To respond to the message, please
ppkarwasz commented on PR #5:
URL:
https://github.com/apache/logging-log4j-jakarta/pull/5#issuecomment-1824930468
@dependabot rebase
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
