The Apache Log4j 2 team is pleased to announce the Log4j 2.13.0 release!
Apache Log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to Log4j that provides significant improvements over its
predecessor, Log4j 1.x, and provides many other modern features such
t; Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Gary
>
> On Thu, Dec 12, 2019 at 1:11 AM Ralph Goers
> wrote:
>
>> This is a vote to release Log4j 2.
ndows"
Gary
On Thu, Dec 12, 2019 at 1:11 AM Ralph Goers
wrote:
> This is a vote to release Log4j 2.13.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don'
+1
Remko.
> On Dec 12, 2019, at 15:11, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.13.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -
the morning if
> everything passes.
>
> On Fri, Dec 13, 2019, at 23:03, Ralph Goers wrote:
> > This vote has now been open for 2 days with no feedback. Please vote.
> >
> > Ralph
> >
> > > On Dec 11, 2019, at 11:11 PM, Ralph Goers
> > > wrote:
ase vote.
>
> Ralph
>
> > On Dec 11, 2019, at 11:11 PM, Ralph Goers
> > wrote:
> >
> > This is a vote to release Log4j 2.13.0, the next version of the Log4j 2
> > project.
> >
> > Please download, test, and cast your votes on the log4j develop
This vote has now been open for 2 days with no feedback. Please vote.
Ralph
> On Dec 11, 2019, at 11:11 PM, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.13.0, the next version of the Log4j 2
> project.
>
> Please download, test, and cast your votes on the log
This is a vote to release Log4j 2.13.0, the next version of the Log4j 2 project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All vote
rg.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>>>>>>>>>> at
>>>>>>>>>>>
>>>>>>>
>>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>>>>&
at
>>>>>>>>>>
>>>>>>
>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>>>>>>>>>> at
>>>>>>>>>>
>>>>>>
>>>
t; org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> >>>>>>>> at
> >>>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> >>>>>>>> at
> >> org.junit.runners.ParentRunner.access$000(ParentRunner.java:
unner.runChildren(ParentRunner.java:288)
>>>>>>>> at
>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>>>>>>>> at
>>>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>>>>>
it4Provider.execute(JUnit4Provider.java:365)
> >>>>>>at
> >>>>>>
> >>
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> >>>>>>at
> >>>>>>
> >>
>
refire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
>>>>>>at
>>>>>>
>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
>>>>>>at
>>>>>>
>> org.apa
fire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> >>>> at
> >>>>
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> >>>> at
> >>>>
> org.apache.maven.surefire.boo
rInSameClassLoader(ForkedBooter.java:384)
>>>> at
>>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
>>>> at
>>>> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
>>>>
orkedBooter.execute(ForkedBooter.java:126)
>>> at
>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
>>> "
>>> [INFO]
>>> [ERROR] Tests run: 643, Failures: 1, Errors: 0, Skipped: 3
>>>
>>> Maybe th
.java:418)
>> "
>> [INFO]
>> [ERROR] Tests run: 643, Failures: 1, Errors: 0, Skipped: 3
>>
>> Maybe this test has some hard-coded EOLs?
>>
>> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
>> Maven home: C:\Java\apache
Files\Java\jdk1.8.0_231\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Gary
>
> Gary
>
> On Mon, Dec 9, 2019 at 12:16 AM Ralph Goers
> wrot
am
Files\Java\jdk1.8.0_231\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Gary
Gary
On Mon, Dec 9, 2019 at 12:16 AM Ralph Goers
wrote:
> This is a vote to release Log4j 2.1
This is a vote to release Log4j 2.13.0, the next version of the Log4j 2 project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All vote
And I’ve still been doing most of my work in the master branch lately, so I
have nothing outstanding to merge for this release.
On Sat, Dec 7, 2019 at 17:07 Carter Kozak wrote:
> Thanks for the heads up and sorry for the delay, it has been a busy week.
> I've merged the contribution, and I'm in
Thanks for the heads up and sorry for the delay, it has been a busy week. I've
merged the contribution, and I'm in the process of adding release notes and a
regression test now.
-ck
On Sat, Dec 7, 2019, at 02:33, Ralph Goers wrote:
> Carter,
>
> If you are going to fix LOG4J2-2725 you need to
Carter,
If you are going to fix LOG4J2-2725 you need to do it quickly. I have been
applying patches this evening and will probably do some more tomorrow but may
start the release process tomorrow night or Sunday morning.
Ralph
> On Dec 2, 2019, at 10:16 AM, Ralph Goers wrote:
>
> If you like
If you like it you should really thank Mikael. His initial work on this gave me
the idea how to do it. I wish he was able to contribute more these days.
Ralph
> On Dec 2, 2019, at 9:49 AM, Carter Kozak wrote:
>
> Thanks Ralph,
>
> Your work on log4j1 configuration compatibility looks fantast
Thanks Ralph,
Your work on log4j1 configuration compatibility looks fantastic!
I'd like to make sure the fix for LOG4J2-2725 goes into this release, if the PR
author doesn't reply in the next day or so I'll take care of it. There are a
couple related places I'd like to test for similar types of
I have finished all the work on new features I wanted to add for the next
release. The latest feature I added is Log4j 2 will now support Log4j 1 xml and
properties file configurations. I have flagged it as experimental - it either
requires a system property to explicitly enable auto detecting
27 matches
Mail list logo
