Hi guys,
The broken rolling file appender - LOG4J2-1804 (sorry for duplicating it
with LOG4J2-1821)
has a very wide effect on our log collection across many servers,
and it would be a great deal of effort to update and test all the
configuration files to walk around the issue.
My question is - ho
Well, this was the last bug that I saw that was critical to get fixed so I
might start the release today - unless something gets in my way.
Ralph
> On Feb 26, 2017, at 3:18 AM, Shlomi Hazan wrote:
>
> Hi guys,
>
> The broken rolling file appender - LOG4J2-1804 (sorry for duplicating it
> with
Oh - we do have to finalize how to get the new Scala project on the web site
but that actually doesn’t have to be part of the Log4j release.
Ralph
> On Feb 26, 2017, at 9:21 AM, Apache wrote:
>
> Well, this was the last bug that I saw that was critical to get fixed so I
> might start the rele
Great!!!
You're the man!
What does it usually take until artifacts are propagated to maven central ?
On Sun, Feb 26, 2017 at 6:22 PM, Apache wrote:
> Oh - we do have to finalize how to get the new Scala project on the web
> site but that actually doesn’t have to be part of the Log4j release.
>
>
After a release candidate is created, it's up for review for at least 72
hours to be voted on. After that, if there are no issues with the release
candidate, that candidate is promoted to Maven Central (which can take up
to a day to fully mirror across all of Maven Central) and made available to
do
