Me too. I think it's to much bureaucratic overhead with a new repo.
On 2017-07-30 22:48, Gary Gregory wrote:
* "Prepare release of logging-log4j-tools repo (if we want to do that)":
For my buck, I'd prefer to see the log4j-server module in the main repo.
Gary
> On Jul 31, 2017, at 5:59, Gary Gregory wrote:
>
> On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory
> wrote:
>
>> * I think the new logic to avoid logging calls blowing up (
>> ConcurrentModificationException) circumvents the ignoreExceptions
>> settings on appenders.
>>
>
> If wonder if we sh
I just pushed an update that fixes the currently failing tests for JMS and
Flume.
Gary
On Sun, Jul 30, 2017 at 1:59 PM, Gary Gregory
wrote:
> On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory
> wrote:
>
>> * I think the new logic to avoid logging calls blowing up
>> (ConcurrentModificationExceptio
On Sun, Jul 30, 2017 at 1:48 PM, Gary Gregory
wrote:
> * I think the new logic to avoid logging calls blowing up (
> ConcurrentModificationException) circumvents the ignoreExceptions
> settings on appenders.
>
If wonder if we should change the
org.apache.logging.log4j.spi.AbstractLogger.tryLogMe
* I think the new logic to avoid logging calls blowing up
(ConcurrentModificationException) circumvents the ignoreExceptions settings
on appenders.
* "Fix broken JmsServer in log4j-server": I'm not that but that's how I
discovered the above.
* "Prepare release of logging-log4j-tools repo (if we w
Provided I find time this week, I'd like to merge in the properties
simplification stuff I mentioned a little while ago.
On 30 July 2017 at 14:51, Mikael Ståldal wrote:
> * Ensure that Scala API documentation will be present on Log4j website.
>
> * Fix broken JmsServer in log4j-server.
>
> * Pre
* Ensure that Scala API documentation will be present on Log4j website.
* Fix broken JmsServer in log4j-server.
* Prepare release of logging-log4j-tools repo (if we want to do that).
Anything else?
